| 2 |
Approval of Agenda |
|
| R1-2401935 |
Draft Agenda of RAN1#116bis meeting |
RAN1 Chair |
| R1-2401938 |
RAN1#116bis Meeting Timelines, Scope, Process |
RAN1 Chair, ETSI MCC |
| 3 |
Highlights from RAN plenary |
|
| R1-2401936 |
Highlights from RAN#103 |
RAN1 Chair |
| 4 |
Approval of Minutes from previous meetings |
|
| R1-2401937 |
Report of RAN1#116 meeting |
ETSI MCC |
| 5 |
Incoming Liaison Statements |
|
| R1-2401939 |
Reply LS on SL-PRS resource allocation |
RAN2, xiaomi |
| R1-2401940 |
Questions on RAN1 parameter list |
RAN2, CATT |
| R1-2401941 |
Reply LS on UE Capability of Multicast Reception in RRC_INACTIVE |
RAN2, vivo |
| R1-2401942 |
Reply LS on skipping UL transmission and R17 TBoMS |
RAN2, Huawei |
| R1-2401943 |
LS on Parallel Tx Capability |
RAN2, ZTE |
| R1-2401944 |
LS on IUC or DRX in co-channel co-existence |
RAN2, xiaomi |
| R1-2401945 |
Reply LS on MAC CE to activate/deactivate semi-persistent PUCCH report for LTM |
RAN2, Fujitsu |
| R1-2401946 |
LS on NCD-SSB time offset for non-(e)RedCap UEs in TDD |
RAN2, vivo |
| R1-2401947 |
Reply LS on inter-frequency neighbour cells supporting NR dedicated spectrum less than 5 MHz for FR1 |
RAN2, Qualcomm |
| R1-2401948 |
LS on 2-step for eRedCap |
RAN2, Ericsson |
| R1-2401949 |
LS on positioning MAC agreements |
RAN2, Huawei |
| R1-2401950 |
LS to RAN1 on decisions on SLPP |
RAN2, Intel |
| R1-2401951 |
Reply LS on n-TimingAdvanceOffset for PDCCH order RACH |
RAN2, Huawei |
| R1-2401952 |
Reply LS on Rel-18 UL Tx switching for parallel switching on four bands |
RAN2, OPPO |
| R1-2401953 |
Reply LS on the progress update of AI/ML Management specifications in SA5 |
RAN3, ZTE |
| R1-2401954 |
Reply LS on RRC network assistant signalling for advanced receiver on MU-MIMO scenario |
RAN4, China Telecom, CATT |
| R1-2401955 |
LS on timing assumption between source and target cells for R18 LTM cell switch |
RAN4, MediaTek |
| R1-2401956 |
LS on SRS BW aggregation impact on other channels/signals |
RAN4, Huawei |
| R1-2401957 |
Further LS reply on the system parameters for NTN above 10 GHz |
RAN4, Nokia |
| R1-2401958 |
LS reply on Relative Phase/Power Error Requirements within Port Groups for 8TX UE |
RAN4, Nokia |
| R1-2401959 |
LS on SRS and PRS bandwidth aggregation feature for positioning |
RAN4, Ericsson |
| R1-2401960 |
Reply to LS on inter-frequency neighbour cells supporting NR dedicated spectrum less than 5 MHz for FR1 |
RAN4, Huawei |
| R1-2401961 |
Updates on measurement report mapping for Positioning Enhancements WI |
RAN4, Huawei |
| R1-2401962 |
Reply LS on RAN2 agreements for satellite switch with resync |
RAN4, Apple |
| R1-2401963 |
LS on RAN4 UE feature list for Rel-18 (version 3) |
RAN4, CMCC |
| R1-2401964 |
Reply LS on UL Tx switching |
RAN4, vivo |
| R1-2401965 |
LS on per UE energy consumption in RAN |
SA2, Vodafone |
| R1-2401966 |
LS Reply to SA WG5 on LS on new definitions of energy efficiency and energy consumption |
SA2, OPPO |
| R1-2401967 |
Clarification on the requirements for NTZ |
SA2, Ericsson, LG Electronics |
| R1-2401968 |
Reply LS RP-240031 on clarification on requirements for NTZ |
RAN, InterDigital |
| R1-2401969 |
Reply LS RP-240029 on per UE energy consumption in RAN |
RAN, InterDigital |
| R1-2401989 |
Considerations on the system parameters for FR2-NTN |
THALES |
| R1-2402033 |
Discussion on RAN2 LS to RAN1 on decisions on SLPP |
Huawei, HiSilicon |
| R1-2402034 |
Discussion on RAN2 LS on MAC agreements |
Huawei, HiSilicon |
| R1-2402036 |
Draft reply LS on positioning MAC agreements |
Huawei, HiSilicon |
| R1-2402037 |
Draft reply LS on SRS BW aggregation impact on other channels/signals |
Huawei, HiSilicon |
| R1-2402071 |
Reply LS clarify power boosting assumption for MU-MIMO advanced receiver |
Ericsson |
| R1-2402159 |
Draft reply LS on parallel Tx Capability |
ZTE |
| R1-2402182 |
Discussion on LS on 2-step for eRedCap |
ZTE, Sanechips |
| R1-2402183 |
Draft LS reply on 2-step for eRedCap |
ZTE, Sanechips |
| R1-2402197 |
Discussion on RRC network assistant signalling for advanced receiver on MU-MIMO scenario |
vivo |
| R1-2402198 |
Discussion on timing assumption between source and target cells for R18 LTM cell switch |
vivo |
| R1-2402199 |
Discussion on Relative Phase/Power Error Requirements within Port Groups for 8TX UE |
vivo |
| R1-2402200 |
Draft reply LS on 2-step RACH for eRedCap |
vivo |
| R1-2402201 |
Draft reply LS on questions on RAN1 parameter list for Rel-18 NR Positioning |
vivo |
| R1-2402202 |
Draft reply LS on Parallel Tx Capability |
vivo |
| R1-2402203 |
Draft reply LS on positioning MAC agreements |
vivo |
| R1-2402204 |
Draft reply LS on SRS BW aggregation impact on other channels/signals |
vivo |
| R1-2402205 |
Discussion on RAN2 LS on UE Capability of Multicast Reception in RRC_INACTIVE |
vivo |
| R1-2402206 |
Draft reply LS on IUC or DRX in co-channel co-existence |
vivo |
| R1-2402291 |
Discussion on coherency for TDMed and non-TDMed 8-ports SRS |
OPPO |
| R1-2402292 |
Discussion on network assistant signalling for advanced receiver on MU-MIMO |
OPPO |
| R1-2402293 |
Discussion on RAN2 LS on Questions on RAN1 parameter List |
OPPO |
| R1-2402294 |
Draft reply LS on Questions on RAN1 parameter List |
OPPO |
| R1-2402295 |
Discussion on IUC and SL DRX in co-channel coexistence |
OPPO |
| R1-2402296 |
Draft reply LS on IUC and SL DRX in co-channel coexistence |
OPPO |
| R1-2402297 |
Discussion on reply LS for 2-step RACH of RedCap UE |
OPPO |
| R1-2402347 |
Draft reply LS on IUC or DRX in co-channel co-existence |
CATT, CICTCI |
| R1-2402348 |
Discussion on reply LS on 2-step RACH for eRedCap |
CATT |
| R1-2402349 |
Discussion on questions on RAN1 parameter list |
CATT |
| R1-2402350 |
Draft reply LS on questions on RAN1 parameter list |
CATT |
| R1-2402351 |
Discussion on positioning MAC agreements |
CATT |
| R1-2402352 |
Draft reply LS on positioning MAC agreements |
CATT |
| R1-2402353 |
Discussion on SRS BW aggregation impact on other channels/signals |
CATT |
| R1-2402354 |
Draft reply LS on SRS BW aggregation impact on other channels/signals |
CATT |
| R1-2402400 |
Draft reply LS on RAN2 LS on UE Capability of Multicast Reception in RRC_INACTIVE |
vivo |
| R1-2402410 |
Draft reply LS on RRC network assistant signalling for advanced receiver on MU-MIMO scenario |
Samsung |
| R1-2402411 |
Draft reply LS on Parallel Tx Capability |
Samsung |
| R1-2402412 |
Draft reply LS on IUC or DRX in co-channel co-existence |
Samsung |
| R1-2402413 |
Draft Reply LS on 2-step for eRedCap |
Samsung |
| R1-2402414 |
Draft reply LS on questions on RAN1 parameter list |
Samsung |
| R1-2402415 |
Draft reply LS on SRS BW aggregation impact on other channels or signals |
Samsung |
| R1-2402488 |
Discussion on 2-step RACH for eRedCap |
vivo |
| R1-2402503 |
Discussion on RAN4 reply LS on RRC assistant signalling for advanced receiver on MU-MIMO scenario |
China Telecom |
| R1-2402638 |
Draft reply to LS on IUC or DRX in co-channel coexistence |
Xiaomi |
| R1-2402696 |
Draft reply LS for questions on RAN1 positioning parameter list |
ZTE Corporation |
| R1-2402697 |
Discussion on RAN1 positioning parameter list for bandwidth aggregation |
ZTE Corporation |
| R1-2402698 |
Draft reply LS on positioning MAC agreements |
ZTE Corporation |
| R1-2402699 |
Draft reply LS on decisions on SLPP |
ZTE Corporation |
| R1-2402700 |
Draft reply LS on SRS BW aggregation impact on other signals |
ZTE Corporation |
| R1-2402731 |
Discussion on RAN2 LS on positioning MAC agreements |
Sharp |
| R1-2402743 |
Discussion on RAN4 LS on SRS BW aggregation impact on other channels/signals |
OPPO |
| R1-2402744 |
Draft reply LS on SRS BW aggregation impact on other channels/signals |
OPPO |
| R1-2402745 |
Discussion on the LS from RAN2 on positioning MAC agreements |
OPPO |
| R1-2402746 |
Draft reply LS to RAN2 on positioning MAC agreements |
OPPO |
| R1-2402775 |
About reply LS on IUC or DRX in co-channel co-existence |
ZTE, Sanechips |
| R1-2402802 |
Discussion on RAN2 LS on 2-step RA for eRedCap |
CMCC |
| R1-2402810 |
Discussion on LS on IUC or DRX in co-channel co-existence |
LG Electronics |
| R1-2402861 |
On RAN4 LS on the system parameters for NTN above 10 GHz |
Apple |
| R1-2402862 |
Draft Reply LS to RAN2 on IUC or DRX in Co-channel Co-existence |
Apple |
| R1-2402909 |
Draft Reply LS on Questions on RAN1 parameter list |
Nokia |
| R1-2402933 |
Discussion on RAN2 LS on 2-step for eRedCap |
NEC |
| R1-2403001 |
Draft LS reply on RRC network assistant signalling for advanced receiver on MU-MIMO scenario |
Nokia |
| R1-2403150 |
Draft Reply LS on Questions on RAN1 parameter list |
Intel Corporation |
| R1-2403151 |
Draft Reply LS on Positioning MAC agreements |
Intel Corporation |
| R1-2403152 |
Discussion on LS from RAN2 on decisions on SLPP |
Intel Corporation |
| R1-2403153 |
Draft Reply LS on SRS BW aggregation impact on other channels/signals |
Intel Corporation |
| R1-2403163 |
Discussion on LS on Parallel Tx Capability |
Qualcomm Incorporated |
| R1-2403164 |
Discussion on LS on 2-step RACH for eRedCap |
Qualcomm Incorporated |
| R1-2403165 |
Discussion on Reply LS on RRC network assistant signalling for advanced receiver on MU-MIMO scenario |
Qualcomm Incorporated |
| R1-2403166 |
Draft Reply to LS on IUC or DRX in co-channel co-existence |
Qualcomm Incorporated |
| R1-2403216 |
Draft reply LS on Parallel Tx Capability |
NTT DOCOMO, INC. |
| R1-2403311 |
DRAFT Reply LS on Parallel Tx Capability |
Nokia |
| R1-2403319 |
Discussion on LS to RAN1 with Questions on RAN1 parameter list |
Ericsson |
| R1-2403320 |
Discussion on LS to RAN1 on the support of multiple location estimate instances in a single measurement report |
Ericsson |
| R1-2403321 |
Discussion on LS to RAN1 on SRS BW aggregation impact on other channels/signals |
Ericsson |
| R1-2403322 |
Discussion on LS to RAN1 on positioning MAC agreements |
Ericsson |
| R1-2403324 |
On LS on 2-step for eRedCap |
Ericsson |
| R1-2403326 |
Discussion on skipping UL transmission and R17 TBoMS |
Nokia |
| R1-2403333 |
Discussion on RAN4 LS on MU-MIMO advanced receiver |
MediaTek Inc. |
| R1-2403335 |
Discussion on RAN2 LS on UL Tx switching |
MediaTek Inc. |
| R1-2403341 |
Discussion on SRS BW aggregation impact on other channels/signals |
Huawei, HiSilicon |
| R1-2403342 |
Discussion on SRS and PRS bandwidth aggregation feature for positioning |
Huawei, HiSilicon |
| R1-2403343 |
Discussions on LS on IUC or DRX in co-channel co-existence |
Huawei, HiSilicon |
| R1-2403353 |
Discussion on Questions on RAN1 parameter list |
Huawei, HiSilicon |
| R1-2403361 |
Discussion on LS on Parallel Tx Capability |
Huawei, HiSilicon |
| R1-2403362 |
Draft reply LS on 2-step for eRedCap |
Huawei, HiSilicon |
| R1-2403364 |
Discussion on RRC network assistant signalling for advanced receiver on MU-MIMO scenario |
Huawei, HiSilicon |
| R1-2403378 |
Discussion on LS on SRS and PRS bandwidth aggregation feature for positioning |
Ericsson |
| R1-2403383 |
Discussion of RAN2 LS on UL Skipping and TBoMS |
Ericsson |
| R1-2403404 |
Draft Reply to RAN2 LS on positioning MAC agreements |
Nokia |
| R1-2403405 |
Discussion of RAN2 LS on positioning MAC agreements |
Nokia |
| R1-2403617 |
Summary of discussion on RAN2 LS on parallel Tx capability |
Moderator (ZTE) |
| R1-2403618 |
Draft Reply LS on Parallel Tx Capability |
ZTE |
| R1-2403619 |
Reply LS on Parallel Tx Capability |
RAN1, ZTE |
| R1-2403632 |
FL Summary #1 of reply LS on RRC network assistant signalling for advanced receiver on MU-MIMO scenario |
Moderator (China Telecom) |
| R1-2403712 |
LS on Sidelink Feature Co-configuration |
RAN2, OPPO |
| R1-2403746 |
[draft] Reply LS on RRC network assistant signalling for advanced receiver on MU-MIMO scenario |
China Telecom |
| R1-2403750 |
Reply LS on RRC network assistant signalling for advanced receiver on MU-MIMO scenario |
RAN1, China Telecom |
| 7 |
Pre-Rel-18 NR Maintenance |
|
| R1-2402038 |
Discussion on TBS limitation for HARQ retransmissions with reserved MCS |
Huawei, HiSilicon |
| R1-2402067 |
Discussion on SRS power scaling |
ZTE |
| R1-2402133 |
Correction of references in TS38.215 |
Intel Corporation |
| R1-2402160 |
Discussion on the maximal HARQ process numbers for TN |
ZTE, CMCC, China Telecom, Ericsson, Nokia, Nokia Shanghai Bell, CATT, Verizon |
| R1-2402161 |
Discussion on CSI dropping with UCI multiplexing on PUSCH |
ZTE |
| R1-2402162 |
Discussion on the multiplexing prioritization for a PUSCH without a TB |
ZTE |
| R1-2402171 |
Discussion on SRS transmission occasion and power scaling |
New H3C Technologies Co., Ltd. |
| R1-2402172 |
Discussion on correction on UCI multiplexing in a PUSCH transmission |
New H3C Technologies Co., Ltd. |
| R1-2402207 |
Discussion on SRS power scaling |
vivo |
| R1-2402208 |
Draft CR on SRS power scaling |
vivo |
| R1-2402209 |
Draft CR on correction on center frequency of initial DL BWP for SDT by a RedCap UE |
vivo |
| R1-2402210 |
Draft CR on correction on center frequency of initial DL BWP for SDT by a RedCap UE |
vivo |
| R1-2402270 |
Draft CR on Collision Handling between PUCCH and SRS |
Google |
| R1-2402271 |
Discussion on Collision Handling between PUCCH and SRS |
Google |
| R1-2402272 |
Draft CR on SRS power scaling |
Google |
| R1-2402273 |
Discussion on SRS power scaling |
Google |
| R1-2402298 |
Discussion on SRS transmission occasion and power scaling |
OPPO |
| R1-2402355 |
Discussion on SRS transmission occasion and power scaling |
CATT |
| R1-2402356 |
Correction on power control for SRS in unified TCI framework |
CATT |
| R1-2402401 |
Draft CR on Type 1A search space definition for SDT |
vivo |
| R1-2402402 |
Draft CR on Type 1A search space definition for SDT |
vivo |
| R1-2402416 |
Discussion on SRS transmission occasion |
Samsung |
| R1-2402417 |
Draft CR for Correcting Channel Access Procedures in NR-U |
Samsung, Ericsson, Nokia, LG Electronics, Huawei, ZTE, Lenovo |
| R1-2402418 |
Draft CR for Correcting Channel Access Procedures in NR-U (Mirrored to Rel-17) |
Samsung, Ericsson, Nokia, LG Electronics, Huawei, ZTE, Lenovo |
| R1-2402419 |
Draft CR for Correcting Channel Access Procedures in NR-U (Mirrored to Rel-18) |
Samsung, Ericsson, Nokia, LG Electronics, Huawei, ZTE, Lenovo |
| R1-2402420 |
Discussion on remaining issues related to Msg3 PUSCH |
Samsung |
| R1-2402421 |
Draft CR for overlapping between msg3 PUSCH and other UL channels |
Samsung |
| R1-2402422 |
Draft CR on HARQ-ACK skipping for BWP switching |
Samsung |
| R1-2402423 |
Discussion on HARQ-ACK skipping for BWP switching |
Samsung |
| R1-2402424 |
Discussion on the timeline issue for UCI multiplexing during HARQ-ACK overriding procedure |
Samsung |
| R1-2402425 |
Correction on timeline requirement for UCI multiplexing |
Samsung |
| R1-2402426 |
Discussion on intra-UE multiplexing and prioritization |
Samsung |
| R1-2402427 |
Correction on UCI multiplexing in a PUSCH transmission |
Samsung |
| R1-2402428 |
Discussion on multiplexing HARQ-ACK in a PUSCH transmission |
Samsung |
| R1-2402429 |
Correction on multiplexing HARQ-ACK in a PUSCH transmission |
Samsung |
| R1-2402430 |
Correction on multiplexing HARQ-ACK in a PUSCH transmission |
Samsung |
| R1-2402504 |
Draft Correction on DMRS bundling for non-back-to-back transmission |
China Telecom |
| R1-2402548 |
Discussion on SRS power scaling |
CMCC |
| R1-2402549 |
Draft CR on SRS power scaling |
CMCC |
| R1-2402707 |
Draft CR on definition of multicast repetition value for Type-1 HARQ-ACK codebook |
CATT, ZTE, Qualcomm, CBN, China broadnet, vivo, MediaTek, Nokia |
| R1-2402716 |
Correction on sdt regarding type-2 RA procedure |
ASUSTeK |
| R1-2402863 |
Views on multiplexing UCI on MSG3 PUSCH |
Apple |
| R1-2402864 |
Clarifications on Type-2 CG PUSCH for a HD UE in TDD CA |
Apple |
| R1-2402945 |
On R17 UE behavior without mux-HARQ-ACK-withoutPUCCH-onPUSCH-r16 |
MediaTek |
| R1-2403097 |
SRS Tx occasion and power scaling |
Ericsson |
| R1-2403098 |
Aperiodic SRS Carrier Switching |
Ericsson |
| R1-2403167 |
Clarification on UCI multiplexing behavior when simultaneousHARQ-ACK-CSI is not provided |
Qualcomm Incorporated |
| R1-2403168 |
Discussion On UCI multiplexing in Msg3 |
Qualcomm Incorporated |
| R1-2403217 |
Remaining issues on aperiodic triggering support for SRS carrier switching |
NTT DOCOMO, INC. |
| R1-2403218 |
Draft CR on sizeDCI-4-2 for MBS |
NTT DOCOMO, INC. |
| R1-2403312 |
Ambiguities in SCell A-CSI reporting UE capabilities |
Nokia |
| R1-2403313 |
On maxRank configuration restriction with fullpowerMode1 and transform precoding ‘enabled’ |
Nokia |
| R1-2403314 |
Correction to maxRank configuration restriction with fullpowerMode1 and transform precoding ‘enabled’ |
Nokia |
| R1-2403315 |
Discussion continuation on the multiplexing/prioritization for a PUSCH without a TB |
Nokia |
| R1-2403316 |
On not multiplexing UCI on MSG3 PUSCH |
Nokia, Ericsson |
| R1-2403317 |
Clarification on not multiplexing UCI on MSG3 PUSCH |
Nokia, Nokia Shanghai Bell, CATT, Ericsson |
| R1-2403344 |
Clarification on modulation order of Msg3 when higher layer parameter tp-pi2BPSK is configured |
Huawei, HiSilicon |
| R1-2403355 |
Correction on Reference RS for SRS Tx beam in unified TCI framework |
Huawei, HiSilicon |
| R1-2403359 |
Discussion on the multiplexing prioritization for a PUSCH without a TB |
Huawei, HiSilicon |
| R1-2403363 |
Discussion on SRS transmission occasion and power scaling |
Huawei, HiSilicon |
| R1-2403384 |
Correction on Multi-Resource SRS Port Power Scaling |
Ericsson |
| R1-2403385 |
Correction on Multiple Triggers of SRS Carrier Switching |
Ericsson |
| R1-2403392 |
Correction on PUSCH power control for mTRP |
Ericsson |
| R1-2403400 |
Discussion on UCI multiplexing and PUSCH prioritization including PUSCH without a TB |
Ericsson |
| R1-2403486 |
Summary of NR maintenance discussion for aperiodic triggering support for SRS carrier switching |
Moderator (Ericsson) |
| R1-2403533 |
Summary#1 of discussions on SDT search space monitoring in initial DL BWP for RedCap |
Moderator (vivo) |
| R1-2403546 |
Correction on sdt regarding type-2 RA procedure |
ASUSTeK, Samsung |
| R1-2403550 |
Correction of references in TS38.215 |
Intel Corporation |
| R1-2403551 |
Correction of references in TS38.215 |
Intel Corporation |
| R1-2403552 |
Moderator summary 1 for R1-2402945 about mux-HARQ-ACK-withoutPUCCH-onPUSCH-r16 |
Moderator (MediaTek Inc.) |
| R1-2403553 |
Moderator summary 2 for R1-2402945 about mux-HARQ-ACK-withoutPUCCH-onPUSCH-r16 |
Moderator (MediaTek Inc.) |
| R1-2403565 |
CR for Correcting Channel Access Procedures in NR-U |
Samsung, Ericsson, Nokia, LG Electronics, Huawei, ZTE, Lenovo, vivo, OPPO |
| R1-2403566 |
CR for Correcting Channel Access Procedures in NR-U (Mirrored to Rel-17) |
Samsung, Ericsson, Nokia, LG Electronics, Huawei, ZTE, Lenovo, vivo, OPPO |
| R1-2403567 |
CR for Correcting Channel Access Procedures in NR-U (Mirrored to Rel-18) |
Samsung, Ericsson, Nokia, LG Electronics, Huawei, ZTE, Lenovo, vivo, OPPO |
| R1-2403584 |
FL summary of maintenance for Rel-17 NR coverage enhancements |
Moderator (China Telecom) |
| R1-2403589 |
Discussion on Collision Handling Between PUCCH and SRS |
Moderator (Google) |
| R1-2403593 |
[116bis-Pre-R18-NR] Summary of UCI multiplexing on PUSCH when simultaneousHARQ-ACK-CSI is not provided |
Moderator (Nokia) |
| R1-2403594 |
[116bis-Pre-R18-NR] Summary on SCell A-CSI reporting UE capabilities |
Moderator (Nokia) |
| R1-2403595 |
[116bis-Pre-R18-NR] Summary of maxRank configuration restriction with fullpowerMode1 and transform precoding ‘enabled’ |
Moderator (Nokia) |
| R1-2403596 |
[116bis-Pre-R18-NR] Summary of UCI multiplexing on Msg3 PUSCH |
Moderator (Nokia) |
| R1-2403597 |
Summary#1 of discussion on SRS transmission occasion and power scaling |
Moderator (vivo) |
| R1-2403598 |
Summary of discussion on intra-UE multiplexing and prioritization |
Moderator (Samsung) |
| R1-2403599 |
Summary of discussion on multiple DAI values for a UL DCI format |
Moderator (Samsung) |
| R1-2403600 |
Summary of discussion on timeline requirements for HARQ-ACK overriding |
Moderator (Samsung) |
| R1-2403606 |
FL summary #1 of Type-2 CG PUSCH for a HD UE in TDD CA |
Moderator (Apple) |
| R1-2403607 |
Moderator summary on Correction on Reference RS for SRS Tx beam in unified TCI framework |
Moderator (Huawei) |
| R1-2403623 |
Summary#2 of discussions on SDT search space monitoring in initial DL BWP for RedCap |
Moderator (vivo) |
| R1-2403624 |
CR on correction on center frequency of initial DL BWP for SDT by a RedCap UE |
Moderator (vivo), Nokia, Samsung, Ericsson, New H3C, ASUSTeK, ZTE, Sanechips |
| R1-2403625 |
CR on correction on center frequency of initial DL BWP for SDT by a RedCap UE |
Moderator (vivo), Nokia, Samsung, Ericsson, New H3C, ASUSTeK, ZTE, Sanechips |
| R1-2403626 |
Summary #1 of discussion on clarification on modulation order of Msg3 when higher layer parameter tp-pi2BPSK is configured |
Moderator (Huawei) |
| R1-2403634 |
Summary of discussion on the maximal HARQ process numbers for TN |
Moderator (ZTE) |
| R1-2403640 |
Summary of definition of multicast repetition for Type-1 HARQ-ACK codebook |
Moderator (CATT) |
| R1-2403644 |
FL summary#2 of maintenance for Rel-17 NR coverage enhancements |
Moderator (China Telecom) |
| R1-2403648 |
RAN1 agreements for Rel-17 NR RedCap |
Rapporteur (Ericsson) |
| R1-2403651 |
Session notes for 7 Pre-Rel-18 NR Maintenance (ad-hoc session) |
Ad-Hoc Chair (Huawei) |
| R1-2403677 |
Correction on modulation order of Msg3 when higher layer parameter tp-pi2BPSK is configured |
Moderator (Huawei), HiSilicon, New H3C, Ericsson, Samsung |
| R1-2403706 |
Summary #2 of discussion on intra-UE multiplexing and prioritization |
Moderator (Samsung) |
| R1-2403707 |
Summary #2 of discussion on multiple DAI values for a UL DCI format |
Moderator (Samsung) |
| R1-2403722 |
[116bis-Pre-R18-NR] Summary#2 of UCI multiplexing on Msg3 PUSCH |
Moderator (Nokia) |
| R1-2403723 |
Correction on sdt regarding type-2 RA procedure |
Moderator (ASUSTeK), Samsung, New H3C, vivo, Ericsson |
| R1-2403724 |
Correction on sdt regarding type-2 RA procedure |
Moderator (ASUSTeK), Samsung, New H3C, vivo, Ericsson |
| R1-2403726 |
Correction to maxRank configuration restriction with fullpowerMode1 and transform precoding ‘enabled’ |
Moderator (Nokia) |
| R1-2403733 |
Draft CR on sizeDCI-4-2 for MBS |
Moderator (NTT DOCOMO, INC.) |
| R1-2403734 |
Summary for discussion of CR on sizeDCI-4-2 |
Moderator (NTT DOCOMO, INC.) |
| R1-2403744 |
Summary#2 of definition of multicast repetition for Type-1 HARQ-ACK codebook |
Moderator (CATT) |
| R1-2403745 |
Summary of discussions on Type-2 HARQ-ACK codebook and DL BWP change |
Moderator (Samsung) |
| R1-2403753 |
[116bis-Pre-R18-NR] Summary of correction on power control for SRS in unified TCI framework |
Moderator (CATT) |
| R1-2403757 |
Draft CR on DMRS bundling for non-back-to-back transmission |
Moderator (China Telecom) |
| R1-2403758 |
CR on DMRS bundling for non-back-to-back transmission |
Moderator (China Telecom), Samsung |
| R1-2403759 |
Draft LS on the capability mux-HARQ-ACK-withoutPUCCH-onPUSCH-r16 |
MediaTek Inc. |
| R1-2403760 |
LS on the capability mux-HARQ-ACK-withoutPUCCH-onPUSCH-r16 |
RAN1, MediaTek Inc. |
| R1-2403761 |
Correction on modulation order of Msg3 when higher layer parameter tp-pi2BPSK is configured |
Moderator (Huawei), HiSilicon, New H3C, Ericsson, Samsung |
| R1-2403762 |
CR on DMRS bundling for non-back-to-back transmission |
Moderator (China Telecom), Samsung |
| R1-2403764 |
Summary #2 of discussion on clarification on modulation order of Msg3 when higher layer parameter tp-pi2BPSK is configured |
Moderator (Huawei) |
| R1-2403771 |
Correction to maxRank configuration restriction with fullpowerMode1 and transform precoding 'enabled' |
Nokia, CATT, Ericsson, Samsung |
| R1-2403772 |
Correction to maxRank configuration restriction with fullpowerMode1 and transform precoding 'enabled' |
Nokia, CATT, Ericsson, Samsung |
| R1-2403773 |
Correction to maxRank configuration restriction with fullpowerMode1 and transform precoding 'enabled' |
Nokia, CATT, Ericsson, Samsung |
| R1-2403784 |
Final summary of NR maintenance discussion for aperiodic triggering support for SRS carrier switching |
Moderator (Ericsson) |
| R1-2403797 |
Rel-16 editorial corrections for TS 38.212 |
Huawei |
| R1-2403798 |
Rel-17 editorial corrections for TS 38.212 |
Huawei |
| R1-2403801 |
Rel-16 editorial corrections for TS 38.212 (mirrored to Rel-17) |
Huawei |
| R1-2403802 |
Rel-16 editorial corrections for TS 38.212 (mirrored to Rel-18) |
Huawei |
| R1-2403803 |
Rel-17 editorial corrections for TS 38.212 (mirrored to Rel-18) |
Huawei |
| R1-2403807 |
Rel-17 editorial corrections for TS 38.213 |
Samsung |
| R1-2403809 |
Rel-17 editorial corrections for TS 38.213 (mirrored to Rel-18) |
Samsung |
| 8 |
Maintenance on Release 18 |
|
| R1-2403793 |
Maintenance of NR Sidelink operation on shared spectrum |
Ericsson |
| R1-2403794 |
Corrections to positioning enhancements |
Ericsson |
| R1-2403795 |
Corrections to sidelink enhancements |
Ericsson |
| R1-2403796 |
Corrections on Rel-18 Multi-carrier enhancements in 38.212 |
Huawei |
| R1-2403799 |
Rel-18 editorial corrections for TS 38.212 |
Huawei |
| R1-2403800 |
Corrections on Rel-18 MIMO Evolution for Downlink and Uplink in 38.212 |
Huawei |
| R1-2403804 |
Maintenance of multi-carrier enhancements for NR |
Samsung |
| R1-2403805 |
Maintenance of MIMO Evolution for Downlink and Uplink |
Samsung |
| R1-2403806 |
Maintenance of expanded and improved NR positioning |
Samsung |
| R1-2403808 |
Rel-18 editorial corrections for TS 38.213 |
Samsung |
| R1-2403810 |
Corrections on enhanced reduced capability NR devices and on TDRA table of multicast PDSCH in RRC INACTIVE state |
Nokia |
| R1-2403811 |
Corrections on Multi-Carrier Enhancements for NR |
Nokia |
| R1-2403812 |
Correction of specification support for MIMO enhancements |
Nokia |
| R1-2403813 |
Corrections on the support for Expanded and Improved NR Positioning |
Nokia |
| R1-2403814 |
Summary of email discussion [Post-116bis-R18-38.212-NR_MC_enh-Core] |
Moderator (Huawei) |
| 8.1 |
Maintenance on NR MIMO Evolution for Downlink and Uplink |
|
| R1-2402021 |
Maintenance of Rel-18 MIMO |
Huawei, HiSilicon |
| R1-2402058 |
Maintenance on NR MIMO Evolution for Downlink and Uplink |
ZTE |
| R1-2402069 |
Maintenance on NR MIMO evolution |
Ericsson |
| R1-2402087 |
Rel-18 NR-MIMO Maintenance |
InterDigital, Inc. |
| R1-2402088 |
FL Summary on Maintenance of 8TX; First Round |
Moderator (InterDigital, Inc.) |
| R1-2402089 |
FL Summary on Maintenance of 8TX; Second Round |
Moderator (InterDigital, Inc.) |
| R1-2402181 |
Moderator summary for maintenance of Rel-18 MIMO on unified TCI extension |
Moderator (MediaTek Inc.) |
| R1-2402211 |
Maintenance on Rel-18 NR MIMO Evolution |
vivo |
| R1-2402274 |
Maintenance on NR MIMO Evolution |
Google |
| R1-2402299 |
Text proposals on NR MIMO Evolution for Downlink and Uplink |
OPPO |
| R1-2402357 |
Maintenance on NR MIMO Evolution for Downlink and Uplink |
CATT |
| R1-2402431 |
Maintenance issues for Rel-18 NR MIMO |
Samsung |
| R1-2402501 |
Maintenance on SRS for 8Tx |
Lenovo |
| R1-2402550 |
Maintenance on NR MIMO evolution for downlink and uplink |
CMCC |
| R1-2402627 |
Maintenance on Rel-18 MIMO |
LG Electronics |
| R1-2402639 |
Maintenance on NR MIMO Evolution for Downlink and Uplink |
Xiaomi |
| R1-2402784 |
Discussion on maintenance issue of Rel-18 MIMO |
Fujitsu |
| R1-2402837 |
Maintenance on NR MIMO Evolution for Downlink and Uplink |
Nokia |
| R1-2403112 |
Maintenance on NR MIMO Evolution for Downlink and Uplink |
Sharp |
| R1-2403169 |
Maintenance on NR MIMO Evolution for Downlink and Uplink |
Qualcomm Incorporated |
| R1-2403219 |
Remaining issues on NR MIMO Evolution for Downlink and Uplink |
NTT DOCOMO, INC. |
| R1-2403411 |
Moderator Summary for maintenance issues on Rel-18 CSI enhancements |
Moderator (Samsung) |
| R1-2403413 |
Summary on Rel-18 STxMP |
Moderator (OPPO) |
| R1-2403417 |
FL summary#1 on DMRS |
Moderator (NTT DOCOMO) |
| R1-2403428 |
FL Summary #1 on SRS enhancements |
Moderator (FUTUREWEI) |
| R1-2403467 |
Moderator Summary on Two TAs for multi-DCI |
Moderator (Ericsson) |
| R1-2403518 |
Second moderator summary for maintenance of Rel-18 MIMO on unified TCI extension |
Moderator (MediaTek Inc.) |
| R1-2403522 |
Summary#2 on Rel-18 STxMP |
Moderator (OPPO) |
| R1-2403562 |
Moderator Summary #2 on Two TAs for multi-DCI |
Moderator (Ericsson) |
| R1-2403638 |
Final moderator summary for maintenance of Rel-18 MIMO on unified TCI extension |
Moderator (MediaTek Inc.) |
| R1-2403689 |
[Draft] LS on two TAs for intra-cell multi-DCI based Multi-TRP operation |
Moderator (Ericsson) |
| R1-2403752 |
LS on two TAs for intra-cell multi-DCI based Multi-TRP operation |
RAN1, Ericsson |
| 8.2 |
Maintenance on Expanded and Improved NR Positioning |
|
| R1-2402035 |
Maintenance of Rel-18 positioning |
Huawei, HiSilicon |
| R1-2402092 |
Maintenance on Expanded and Improved NR Positioning |
Nokia |
| R1-2402142 |
Maintenance issues on Rel-18 Positioning |
Intel Corporation |
| R1-2402212 |
Maintenance on Rel-18 Positioning |
vivo |
| R1-2402300 |
Text Proposals on Expanded and Improved NR Positioning |
OPPO |
| R1-2402358 |
Maintenance on Expanded and Improved NR Positioning |
CATT, CICTCI |
| R1-2402432 |
Remaining Issues on NR positioning |
Samsung |
| R1-2402701 |
Maintenance on expanded and improved NR positioning |
ZTE Corporation |
| R1-2402865 |
Remaining Issues on Expanded and Improved Positioning |
Apple |
| R1-2403104 |
Maintenance on Resource allocation for SL PRS |
ASUSTeK |
| R1-2403170 |
Maintenance on Expanded and Improved NR Positioning |
Qualcomm Incorporated |
| R1-2403263 |
Maintenance of expanded and improved NR positioning |
LG Electronics |
| R1-2403318 |
Remaining issues on expanded and improved NR positioning |
Ericsson |
| R1-2403410 |
Maintenance on Expanded and Improved NR Positioning |
CATT, CICTCI |
| R1-2403419 |
FL Summary #1 for maintenance on NR DL and UL carrier phase positioning |
Moderator (CATT) |
| R1-2403420 |
FL Summary #2 for maintenance on NR DL and UL carrier phase positioning |
Moderator (CATT) |
| R1-2403426 |
Summary #1 for BW aggregation positioning |
Moderator (ZTE) |
| R1-2403427 |
Summary #2 for BW aggregation positioning |
Moderator (ZTE) |
| R1-2403465 |
FL summary #1 on SL positioning reference signal |
Moderator (Intel Corporation) |
| R1-2403466 |
FL summary #2 on SL positioning reference signal |
Moderator (Intel Corporation) |
| R1-2403519 |
Feature Lead summary #1 for Positioning for RedCap UEs |
Moderator (Ericsson) |
| R1-2403520 |
Feature Lead summary #2 for Positioning for RedCap UEs |
Moderator (Ericsson) |
| R1-2403521 |
Feature Lead summary #3 for Positioning for RedCap UEs |
Moderator (Ericsson) |
| R1-2403534 |
FLS#1 on reply LS on positioning MAC agreements |
Moderator (Huawei) |
| R1-2403535 |
Draft reply LS on positioning MAC agreements |
Moderator (Huawei) |
| R1-2403536 |
Reply LS on positioning MAC agreements |
RAN1, Huawei |
| R1-2403537 |
FLS#1 on LS reply on SRS BW aggregation impact on other channels/signals |
Moderator (Huawei) |
| R1-2403538 |
Draft reply LS on SRS BW aggregation impact on other channels/signals |
Moderator (Huawei) |
| R1-2403539 |
Reply LS on SRS BW aggregation impact on other channels/signals |
RAN1, Huawei |
| R1-2403543 |
Moderator Summary #0 on resource allocation for SL PRS |
Moderator (Qualcomm) |
| R1-2403544 |
FL Summary for the reply LS on RAN2’s questions on RAN1 parameter list |
Moderator (CATT) |
| R1-2403547 |
Summary #1 on Measurements and reporting for SL positioning |
Moderator (vivo) |
| R1-2403548 |
Summary #2 on Measurements and reporting for SL positioning |
Moderator (vivo) |
| R1-2403564 |
Moderator Summary #1 on resource allocation for SL PRS |
Moderator (Qualcomm) |
| R1-2403576 |
Draft LS on UE’s reporting SL PRS CBR measurement to gNB |
Qualcomm Incorporated |
| R1-2403577 |
LS on UE’s reporting SL PRS CBR measurement to gNB |
RAN1, Qualcomm Incorporated |
| R1-2403612 |
Summary #3 for BW aggregation positioning |
Moderator (ZTE) |
| R1-2403620 |
Corrections on the support for Expanded and Improved NR Positioning |
Intel Corporation (Moderator), CATT, CICTCI |
| R1-2403621 |
Draft reply LS on decisions on SLPP |
vivo |
| R1-2403622 |
Reply LS on decisions on SLPP |
RAN1, vivo |
| R1-2403635 |
Draft reply LS on questions on RAN1 parameter list |
CATT |
| R1-2403636 |
Reply LS on questions on RAN1 parameter list |
RAN1, CATT |
| R1-2403652 |
Session notes for 8.2 (Maintenance on expanded and improved NR positioning) |
Ad-Hoc Chair (Huawei) |
| R1-2403717 |
Draft LS on PRS resource ID for bandwidth aggregation |
Moderator (ZTE) |
| R1-2403728 |
LS on PRS resource ID for bandwidth aggregation |
RAN1, ZTE |
| R1-2403731 |
Draft LS on the dci-FormatsSL and DCI format 3_2 |
Qualcomm Incorporated |
| R1-2403732 |
LS on the dci-FormatsSL and DCI format 3_2 |
RAN1, Qualcomm Incorporated |
| R1-2403742 |
List of RAN1 agreements for Rel-18 Positioning |
Moderator (Intel Corporation) |
| 8.3 |
Maintenance on Multi-Carrier Enhancements for NR |
|
| R1-2402032 |
Maintenance of Rel-18 Multicarrier Enhancements |
Huawei, HiSilicon |
| R1-2402068 |
Correction on DCI format 1_3 with SRS carrier switching |
ZTE |
| R1-2402093 |
Remaining issues on Multi-Carrier Enhancements for NR |
Spreadtrum Communications |
| R1-2402163 |
Maintenance on Multi-Carrier Enhancements for NR |
ZTE |
| R1-2402213 |
Maintenance on Multi-Carrier Enhancements for NR |
vivo |
| R1-2402301 |
Maintenance of multi-carrier enhancement for NR |
OPPO |
| R1-2402359 |
Maintenance on Multi-Carrier Enhancements for NR |
CATT |
| R1-2402433 |
Remaining issues on multi-cell PUSCH/PDSCH scheduling with a single DCI |
Samsung |
| R1-2402527 |
Maintenance on Multi-Carrier Enhancements for NR |
Langbo |
| R1-2402584 |
Remaining issues on Rel-18 multi-carrier enhancements |
Lenovo |
| R1-2402640 |
Remaining issues on Multi-Carrier Enhancements for NR |
Xiaomi |
| R1-2402932 |
On Rel-18 MC-DCI scheduling |
Nokia |
| R1-2403114 |
Remaining issues on multi-cell scheduling with single DCI |
LG Electronics |
| R1-2403171 |
Maintenance on Rel-18 multicarrier enhancements |
Qualcomm Incorporated |
| R1-2403220 |
Maintenance on Multi-Carrier Enhancements for NR |
NTT DOCOMO, INC. |
| R1-2403269 |
Maintenance for Rel-18 multi-carrier enhancements |
Ericsson |
| R1-2403429 |
Summary of discussion on Multi-carrier UL Tx switching scheme |
Moderator (NTT DOCOMO, INC.) |
| R1-2403477 |
Feature lead summary#1 on multi-cell PUSCH/PDSCH scheduling with a single DCI |
Moderator (Lenovo) |
| R1-2403478 |
Feature lead summary#2 on multi-cell PUSCH/PDSCH scheduling with a single DCI |
Moderator (Lenovo) |
| R1-2403479 |
Feature lead summary#3 on multi-cell PUSCH/PDSCH scheduling with a single DCI |
Moderator (Lenovo) |
| R1-2403613 |
Summary#2 of discussion on Multi-carrier UL Tx switching scheme |
Moderator (NTT DOCOMO, INC.) |
| R1-2403781 |
Summary#3 of discussion on Multi-carrier UL Tx switching scheme |
Moderator (NTT DOCOMO, INC.) |
| R1-2403783 |
Feature lead summary#4 on multi-cell PUSCH/PDSCH scheduling with a single DCI |
Moderator (Lenovo) |
| R1-2403785 |
Feature lead summary#5 on multi-cell PUSCH/PDSCH scheduling with a single DCI |
Moderator (Lenovo) |
| 8.4 |
Maintenance on other Rel-18 work items |
|
| R1-2402002 |
Discussion on RAN1 impact to support the RAN4 work on NTN above 10GHz |
Huawei, HiSilicon |
| R1-2402055 |
Draft CR for Parameter Name Alignment for R18 RedCap UEs in TS 38.214 |
FUTUREWEI |
| R1-2402059 |
Draft CR on consistency between SSB index and TCI state in LTM Cell Switch Command MAC CE |
ZTE |
| R1-2402060 |
Discussion on consistency between SSB index and TCI state in LTM Cell Switch Command MAC CE |
ZTE |
| R1-2402061 |
Draft CR on prioritizations for transmission power reductions in LTM |
ZTE |
| R1-2402062 |
Draft CR on capturing CFRA triggered by LTM Cell Switch Command MAC CE |
ZTE |
| R1-2402152 |
Correction of Rel-18 NES cell DTX/DRX operations |
Intel Corporation |
| R1-2402153 |
Discussion on maintenance issues on NES |
Intel Corporation |
| R1-2402214 |
Discussions of the LS on the system parameters for NTN above 10 GHz |
vivo |
| R1-2402215 |
Discussions on correction on timing of first Msg3 repetition in NTN |
vivo |
| R1-2402216 |
Draft CR on correction on timing of first Msg3 repetition in NTN |
vivo |
| R1-2402217 |
Draft CR on alignment on parameter of PDCCH reception for scheduling initial PUSCH in NTN RACH-less handover |
vivo |
| R1-2402218 |
Clarification on COT sharing flag in 38.212 |
vivo |
| R1-2402219 |
Clarification on COT sharing flag in 37.213 |
vivo |
| R1-2402220 |
Clarification on DMRS symbol in 38.211 |
vivo |
| R1-2402221 |
Clarification on PSFCH prioritization in 38.213 |
vivo |
| R1-2402222 |
Clarification on PSFCH power control in 38.213 |
vivo |
| R1-2402223 |
Clarification on CPE determination for PSCCH/PSSCH transmission on a resumed COT in 38.214 |
vivo |
| R1-2402224 |
Draft CR on correction on PRACH repetitions with less than N symbols gap |
vivo |
| R1-2402225 |
Draft CR on timing assumption between source and target cells for R18 LTM cell switch |
vivo |
| R1-2402226 |
Discussion on LTM cell switch for target cell with multiple TAs |
vivo |
| R1-2402275 |
Draft CR on Correction of CSI Report Subconfiguration |
Google |
| R1-2402302 |
Correction on Candidate Cell TCI state indication in TS 38.213 |
OPPO |
| R1-2402303 |
Draft CR for correction on PSFCH power control |
OPPO |
| R1-2402304 |
Draft CR for correction on PSSCH rate matching |
OPPO |
| R1-2402305 |
Draft CR for correction on contention window adjustment |
OPPO |
| R1-2402306 |
Draft CR for correction on PSSCH preparation time for multiple PSFCH occasions |
OPPO |
| R1-2402307 |
Discussion on CPE starting position for S-SSB in SL-U |
OPPO |
| R1-2402308 |
Draft LS on CPE starting position for S-SSB in SL-U |
OPPO |
| R1-2402309 |
Draft CR for correction on CPE starting position for PSCCH/PSSCH |
OPPO |
| R1-2402310 |
Discussion on RAN4 LS for FR2 NTN |
OPPO |
| R1-2402311 |
Discussion on HARQ enhancement for IoT NTN |
OPPO |
| R1-2402312 |
Draft CR on HARQ enhancement for IoT NTN |
OPPO |
| R1-2402360 |
Correction on the condition of multi-channel access procedures for SL transmissions |
CATT, CICTCI |
| R1-2402361 |
Corrections on the description of SCI format 1-A |
CATT, CICTCI |
| R1-2402362 |
Correction on PSFCH power control of SL-U |
CATT, CICTCI |
| R1-2402363 |
Correction on TRIV/FRIV resource indication of SL-U |
CATT, CICTCI |
| R1-2402409 |
Maintenance on Network Energy Savings for NR |
Nokia, Nokia Shanghai Bell |
| R1-2402434 |
Remaining Issues for NR Sidelink Evolution |
Samsung |
| R1-2402435 |
Draft CR for Correcting the CP Extension for PSSCH/PSCCH in TS 38.214 |
Samsung |
| R1-2402436 |
Draft CR for Correcting S-SSB Transmission in Non-Anchor RB Set in TS 38.213 |
Samsung |
| R1-2402437 |
Draft CR for Correcting Power on Common Interlace in PSFCH Power Control in TS 38.213 |
Samsung |
| R1-2402438 |
Draft CR for Editorial Changes in TS 37.213 for Rel-18 SL |
Samsung |
| R1-2402439 |
Draft CR for Editorial Changes in TS 38.211 for Rel-18 SL |
Samsung |
| R1-2402440 |
Draft CR for Editorial Changes in TS 38.212 for Rel-18 SL |
Samsung |
| R1-2402441 |
Draft CR for Editorial Changes in TS 38.213 for Rel-18 SL |
Samsung |
| R1-2402442 |
Draft CR for Editorial Changes in TS 38.214 for Rel-18 SL |
Samsung |
| R1-2402443 |
Draft CR for Editorial Changes in TS 38.215 for Rel-18 SL |
Samsung |
| R1-2402444 |
Draft CR on backhaul link beam determination after link recovery in C-link of an NCR |
Samsung |
| R1-2402445 |
Remaining issues on network energy saving |
Samsung |
| R1-2402446 |
Correction on power assumption for type 1 spatial domain adaptation |
Samsung |
| R1-2402447 |
Correction on Cell DTX operation for CSI report |
Samsung |
| R1-2402448 |
Correction on Cell DTX operation for CSI-RS reception and SRS transmission |
Samsung |
| R1-2402449 |
Remaining issues on multiplexing HARQ-ACK in a PUSCH with repetitions |
Samsung |
| R1-2402450 |
Correction on multiplexing HARQ-ACK in a PUSCH with repetitions |
Samsung |
| R1-2402489 |
Discussion on guardband PRB handling |
vivo |
| R1-2402490 |
Discussion on pre-emption/re-evaluation of MCSt |
vivo |
| R1-2402493 |
Correction on timing assumption between source and target cells for R18 LTM cell switch |
CATT |
| R1-2402502 |
Draft CR on TS38.211 for LTM |
Lenovo |
| R1-2402528 |
Correction on Further NR Mobility Enhancements |
Langbo |
| R1-2402540 |
Remaining issues of Rel-18 network energy saving |
Panasonic |
| R1-2402551 |
Draft CR on TDRA table of multicast PDSCH in RRC INACTIVE state |
CMCC |
| R1-2402591 |
On TEI for HARQ-ACK MUX on PUSCH |
Ericsson |
| R1-2402606 |
Discussion on RAN4 LS on the system parameters for NTN above 10 GHz |
Ericsson |
| R1-2402618 |
Further discussion on LS on the system parameters for NTN above 10 GHz |
ZTE |
| R1-2402636 |
Draft CR on Rel-18 NES with operation of Cell DtxDrx |
Nokia, Nokia Shanghai Bell |
| R1-2402641 |
Draft CR on UE behavior on DCI 2-9 monitoring for network energy saving |
Xiaomi |
| R1-2402642 |
Discussion on 2-step RACH for eRedCap |
Xiaomi |
| R1-2402643 |
Draft CR on CAPC condition for COT resuming for SL-U |
Xiaomi |
| R1-2402644 |
Draft CR on CPE determination mechanism for SL-U |
Xiaomi |
| R1-2402709 |
Draft CR on applying UE-measured TA after LTM Cell Switch Command MAC CE |
ZTE |
| R1-2402710 |
Discussion on applying TCI state indicated in LTM Cell Switch Command MAC CE to a list of CCs |
ZTE |
| R1-2402717 |
Correction on CORESET monitoring regarding RACH less HO |
ASUSTeK |
| R1-2402732 |
Discussion on the minimum time gap between any two selected resources of a TB |
Sharp |
| R1-2402733 |
Correction on determination of starting RB set for PSSCH |
Sharp |
| R1-2402734 |
Correction on determination of PSFCH candidate resources |
Sharp |
| R1-2402735 |
Correction on contiguous RB based resource allocation |
Sharp |
| R1-2402753 |
Draft CR on applicable RB set(s) for COT sharing in TS 37.213 |
NEC |
| R1-2402754 |
Draft CR on PSFCH power control in TS 38.213 |
NEC |
| R1-2402777 |
Correction on SL high layer parameters alignment in TS 38.211 |
ZTE, Sanechips |
| R1-2402778 |
Correction on PSFCH resource mapping for contiguous RB resource pool in TS 38.213 |
ZTE, Sanechips |
| R1-2402779 |
Correction on PSSCH transmission decode behaviour in TS 38.214 |
ZTE, Sanechips |
| R1-2402780 |
Correction on parameter names for section 16.1 in TS 38.213 |
ZTE, Sanechips |
| R1-2402781 |
Correction on parameter names for section 8.1.2.1 in TS 38.214 |
ZTE, Sanechips |
| R1-2402782 |
Correction on resource selection window for mode2 sensing in TS 38.214 |
ZTE, Sanechips |
| R1-2402783 |
Editorial modification on SL channel access priority class in TS 37.213 |
ZTE, Sanechips |
| R1-2402785 |
Correction on TA offset information for UE-based TA acquisition |
Fujitsu |
| R1-2402821 |
Correction on timing difference for LTM |
ASUSTeK |
| R1-2402822 |
Correction on LTM |
ASUSTeK |
| R1-2402866 |
Draft Corrections on PSFCH Power Control for Sidelink on Unlicensed Spectrum |
Apple |
| R1-2402912 |
Correction on Cell DTX operation for PDSCH reception |
Samsung |
| R1-2402983 |
Draft CR for 38.213 on candidate cell naming |
Ericsson |
| R1-2402984 |
Draft CR for 38.213 on deactivation of candidate TCI states |
Ericsson |
| R1-2402985 |
Draft CR for 38.213 on RACH procedure triggred by LTM cell switch |
Ericsson |
| R1-2402986 |
Draft CR for 38.213 on signaling of TCI state in LTM cell switch command |
Ericsson |
| R1-2402987 |
Draft CR for 38.213 on TCI state applied for CORESET 0 |
Ericsson |
| R1-2402988 |
Draft CR for 38.214 on CSI report priority |
Ericsson |
| R1-2402989 |
Draft CR for 38.214 on QCL assumption after LTM cell switch command |
Ericsson |
| R1-2402990 |
Draft CR for 38.214 on spCellInclusion |
Ericsson |
| R1-2402991 |
Remaining issue on beam usage after LTM cell switch command |
Panasonic |
| R1-2402993 |
Maintenance on IoT NTN enhancements |
Nokia, Nokia Shanghai Bell |
| R1-2403007 |
Corrections for clarifications for time offset in preamble transmission in TS 38.213 |
ETRI |
| R1-2403008 |
Discussion for clarifications for time offset in preamble transmission in TS 38.213 |
ETRI |
| R1-2403009 |
Draft CR on L1/L2-triggered mobility procedures |
ETRI |
| R1-2403010 |
Discussion on L1/L2-triggered mobility procedures |
ETRI |
| R1-2403033 |
Correction on CSI report with cell DTX |
ZTE, Sanechips |
| R1-2403034 |
Correction on CSI report for NES |
ZTE, Sanechips |
| R1-2403045 |
Maintenance on NR Network-Controlled Repeaters |
CATT |
| R1-2403073 |
Draft CR for 38.213 on PRACH collision handling for LTM |
Nokia |
| R1-2403074 |
Draft CR for 38.213 on prioritizations for transmission power reductions for LTM |
Nokia |
| R1-2403079 |
Further discussion on NR over NTN operation in frequency bands defined by FR2-NTN |
Nokia, Nokia Shanghai Bell |
| R1-2403083 |
Feature lead summary 1 on FR2-NTN discussions |
Moderator (Nokia) |
| R1-2403084 |
Feature lead summary 2 on FR2-NTN discussions |
Moderator (Nokia) |
| R1-2403085 |
Maintenance on IoT NTN enhancements |
Ericsson |
| R1-2403115 |
CSI-RS resource/port counting for NES |
LG Electronics |
| R1-2403154 |
Correction on total power ramp-up for multiple PRACH transmissions |
Ericsson |
| R1-2403155 |
Draft CR on SL-U TBS determination |
Panasonic |
| R1-2403156 |
Maintenance of NR Sidelink unlicensed spectrum |
Panasonic |
| R1-2403172 |
Impact of cell DRX operation on uplink DMRS bundling |
Qualcomm Incorporated |
| R1-2403173 |
Draft CR for description of Shared Channel Occupancy |
Qualcomm Incorporated |
| R1-2403174 |
Draft CR for wording alignment involving channels and RB sets |
Qualcomm Incorporated |
| R1-2403175 |
Draft CR for exclusion of PRBs in intra cell guardband based on LBT failure |
Qualcomm Incorporated |
| R1-2403176 |
Application time of Cell DRX in NTN |
Qualcomm Incorporated |
| R1-2403177 |
Remaining issues for UE complexity reduction for eRedCap |
Qualcomm Incorporated |
| R1-2403178 |
RO Group Determination for PRACH Repetitions |
Qualcomm Incorporated |
| R1-2403221 |
Maintenance on further UE complexity reduction for eRedCap |
NTT DOCOMO, INC. |
| R1-2403222 |
Maintenance on Further NR Mobility Enhancements |
NTT DOCOMO, INC. |
| R1-2403223 |
Discussion on FR2-NTN |
NTT DOCOMO, INC. |
| R1-2403224 |
Draft CR on CAPC value for PSFCH+S-SSB for SL-U |
NTT DOCOMO, INC. |
| R1-2403225 |
Draft CR on processing time in case of using the 2nd starting symbol for SL-U (38.213) |
NTT DOCOMO, INC. |
| R1-2403226 |
Draft CR on processing time in case of using the 2nd starting symbol for SL-U (38.214) |
NTT DOCOMO, INC. |
| R1-2403227 |
Draft CR on PSFCH prioritization for UE incapable of TX in multi-RB sets for SL-U |
NTT DOCOMO, INC. |
| R1-2403228 |
Maintenance of resource selection in MAC layer for SL-U |
NTT DOCOMO, INC. |
| R1-2403270 |
Draft CR for 38.214 on cell DTX/DRX |
Ericsson |
| R1-2403282 |
Maintenance on IoT NTN enhancements |
Nordic Semiconductor ASA |
| R1-2403288 |
Draft CR for 38.214 on spatial/power domain adaptation |
Ericsson |
| R1-2403289 |
Discussion on RAN4 LS on FR2-NTN aspectshai |
Sharp |
| R1-2403290 |
Correction on OFDM symbol location for PSFCH transmission in SL-U |
Sharp |
| R1-2403291 |
Correction on determination of PSFCH resources for a PSSCH |
Sharp |
| R1-2403292 |
Correction on sidelink starting symbol index for indications of UL slots in PSBCH in SL-U |
Sharp |
| R1-2403293 |
Correction on description of NnonSL slots in SL-U |
Sharp |
| R1-2403294 |
Correction on Multi-channel access procedure for SL transmission in SL-U |
Sharp |
| R1-2403295 |
Discussion on CPE determination for multiple TBs |
Sharp |
| R1-2403296 |
Correction on CPE determination for no sensing result |
Sharp |
| R1-2403297 |
Correction on CAPC determination for multi-channel access procedure for SL |
Sharp |
| R1-2403310 |
Draft CR for 38.213 for TCI state usage after RACH-based LTM |
Panasonic |
| R1-2403325 |
Remaining issues on further NR coverage enhancements |
Nokia, China Telecom |
| R1-2403328 |
Maintenance on Rel-18 eRedCap |
Ericsson |
| R1-2403331 |
Correction on supplementary uplink for LTM |
Google |
| R1-2403334 |
Correction on CFRA triggered by cell switch command |
Google |
| R1-2403337 |
Discussion on LTM TCI state application on target SCell |
Huawei, HiSilicon |
| R1-2403338 |
Discussion on measurement period requirements for UE location verification |
Huawei, HiSilicon |
| R1-2403339 |
TP on successful GNSS reacquisition for IoT NTN |
Huawei, HiSilicon |
| R1-2403340 |
Draft CR on Rel-18 PRACH repetition |
Huawei, HiSilicon |
| R1-2403345 |
Correction on restrictions of performing multi-channel access in TS 37.213 |
Huawei, HiSilicon |
| R1-2403346 |
Draft CR on multicast transmissions for Rel-18 RedCap in inactive mode |
Huawei, HiSilicon |
| R1-2403347 |
Corrections to LTM TCI state application on target SCell in TS38.213 |
Huawei, HiSilicon |
| R1-2403348 |
Discussion on the power control after LTM cell switch and pathloss RS in LTM TCI state |
Huawei, HiSilicon |
| R1-2403349 |
Corrections to the power control after LTM cell switch and Pathloss RS in LTM TCI state in TS38.213 |
Huawei, HiSilicon |
| R1-2403350 |
Corrections to CFRA triggered by cell switch command in TS38.213 |
Huawei, HiSilicon |
| R1-2403351 |
Correction on SRS transmission for cell DRX |
Huawei, HiSilicon |
| R1-2403352 |
Correction on SR transmission for cell DRX |
Huawei, HiSilicon |
| R1-2403356 |
Correction on PSFCH power control |
Huawei, HiSilicon |
| R1-2403357 |
Correction on RRC parameter names for Rel-18 sidelink in TS 38.212 |
Huawei, HiSilicon |
| R1-2403358 |
Correction on RRC parameter names for Rel-18 sidelink in TS 38.214 |
Huawei, HiSilicon |
| R1-2403360 |
Corrections to UL/SUL indicator in DCI format 1_0 for LTM early RACH in TS38.212 |
Huawei, HiSilicon |
| R1-2403368 |
Correction on Type 2A SL channel access for SL transmission over MCSt with multiple starting positions in a slot |
WILUS |
| R1-2403401 |
Correction on multiplexing HARQ-ACK in a PUSCH with repetitions |
Ericsson |
| R1-2403406 |
Draft CR for 38.211 on Introduction of FR2-NTN |
Ericsson, Thales |
| R1-2403407 |
Draft CR for 38.213 on introduction of FR2-NTN |
Ericsson |
| R1-2403408 |
Draft CR for 38.214 on Introduction of FR2-NTN |
Ericsson |
| R1-2403421 |
Feature lead summary #1 of AI 8.4 maintenance of Release 18 IoT NTN |
Moderator (MediaTek) |
| R1-2403438 |
Summary of issues for Rel-18 NES enhancements on cell DTX/DRX mechanism |
Moderator (Intel Corporation) |
| R1-2403439 |
Summary #1 of discussion for Rel-18 NES enhancements on cell DTX/DRX mechanism |
Moderator (Intel Corporation) |
| R1-2403440 |
Summary #2 of discussion for Rel-18 NES enhancements on cell DTX/DRX mechanism |
Moderator (Intel Corporation) |
| R1-2403449 |
FL summary #1 for Rel-18 NR eRedCap maintenance |
Moderator (Ericsson) |
| R1-2403450 |
FL summary #2 for Rel-18 NR eRedCap maintenance |
Moderator (Ericsson) |
| R1-2403451 |
RAN1 agreements for Rel-18 NR eRedCap |
Rapporteur (Ericsson) |
| R1-2403454 |
FL summary #1 for AI 8.4: SL-U channel access mechanism |
Moderator (OPPO) |
| R1-2403455 |
FL summary #2 for AI 8.4: SL-U channel access mechanism |
Moderator (OPPO) |
| R1-2403456 |
FL summary #3 for AI 8.4: SL-U channel access mechanism |
Moderator (OPPO) |
| R1-2403457 |
FL summary for AI 8.4: SL-U channel access mechanism (EOM) |
Moderator (OPPO) |
| R1-2403463 |
FL Summary #1: Maintenance on Rel-18 NR NTN |
Moderator (Thales) |
| R1-2403464 |
FL Summary #2: Maintenance on Rel-18 NR NTN |
Moderator (Thales) |
| R1-2403471 |
FL summary on R18 MBS maintenance |
Moderator (CMCC) |
| R1-2403475 |
FLS#1 for maintenance of SD-PD adaptation R18 NES |
Moderator (Huawei) |
| R1-2403494 |
FL summary#1 for AI 8.4 SL-U physical channel design framework |
Moderator (Huawei) |
| R1-2403495 |
FL summary#2 for AI 8.4 SL-U physical channel design framework |
Moderator (Huawei) |
| R1-2403496 |
FL summary#3 for AI 8.4 SL-U physical channel design framework |
Moderator (Huawei) |
| R1-2403525 |
FL summary 1 of Maintenance on Further NR Mobility Enhancements |
Moderator (Fujitsu) |
| R1-2403526 |
FL summary 2 of Maintenance on Further NR Mobility Enhancements |
Moderator (Fujitsu) |
| R1-2403540 |
Summary#1 of maintenance issues on side control information and NCR behavior |
Moderator (ZTE) |
| R1-2403542 |
FL Summary #1 of maintenance on further NR coverage enhancements |
Moderator (China Telecom) |
| R1-2403545 |
Draft CR on correction on PRACH repetitions with less than N symbols gap |
Moderator (China Telecom), vivo, Samsung |
| R1-2403549 |
Correction on total power ramp-up for multiple PRACH transmissions |
Moderator (China Telecom), Ericsson, Samsung |
| R1-2403556 |
Corrections on RRC parameters for R18 NES spatial/power domain adaptation |
Moderator (Huawei), Ericsson, Google, Nokia, NSB, ZTE, Sanechips, Samsung |
| R1-2403557 |
Corrections on RRC parameters for R18 NES spatial/power domain adaptation |
Moderator (Huawei), Ericsson, Google, Nokia, NSB, ZTE, Sanechips, Samsung |
| R1-2403561 |
Correction on CSI report dropping with cell DTX |
Moderator (Huawei), ZTE, Sanechips, LG Electronics |
| R1-2403572 |
Draft Reply to LS on IUC or DRX in co-channel co-existence |
Moderator (LG Electronics) |
| R1-2403573 |
Reply to LS on IUC or DRX in co-channel co-existence |
RAN1, LG Electronics |
| R1-2403574 |
FL Summary #1 for AI 8.4: LS on IUC or DRX in co-channel co-existence |
Moderator (LG Electronics) |
| R1-2403575 |
FL Summary #2 for AI 8.4: LS on IUC or DRX in co-channel co-existence |
Moderator (LG Electronics) |
| R1-2403578 |
LS on CPE starting position for S-SSB in SL-U |
RAN1, OPPO |
| R1-2403579 |
Correction on restrictions of performing multi-channel access |
Moderator (OPPO), CATT, CICTCI, Huawei, HiSilicon, Qualcomm |
| R1-2403580 |
Correction on CAPC determination in multi-channel access procedure |
Moderator (OPPO), Sharp, Huawei, HiSilicon |
| R1-2403581 |
Draft CR for TS 38.211 for introduction of FR2-NTN |
Moderator (Nokia), NTT DOCOMO, INC. |
| R1-2403582 |
Draft CR for TS 38.213 for introduction of FR2-NTN |
Moderator (Nokia), NTT DOCOMO, INC. |
| R1-2403583 |
Draft CR for TS 38.214 for introduction of FR2-NTN |
Moderator (Nokia), NTT DOCOMO, INC. |
| R1-2403585 |
Correction on PSFCH prioritization for UE incapable of TX in multi-RB sets for SL-U |
Moderator (Huawei), NTT DOCOMO, INC., Qualcomm, vivo |
| R1-2403586 |
Correction on PSSCH preparation time for multiple PSFCH occasions |
Moderator (Huawei), OPPO, Qualcomm, vivo |
| R1-2403587 |
Draft LS on updating RAN1 agreement about minimum time gap Z |
Huawei |
| R1-2403588 |
LS on updating RAN1 agreement about minimum time gap Z |
RAN1, Huawei |
| R1-2403590 |
Draft CR on correction on timing of first Msg3 repetition in NTN |
vivo |
| R1-2403591 |
Correction on CORESET monitoring regarding RACH less HO |
Moderator (Thales) |
| R1-2403592 |
Application time of Cell DRX in NTN |
Moderator (Thales) |
| R1-2403601 |
Summary of discussion on multiplexing HARQ-ACK in a PUSCH repetition |
Moderator (Samsung) |
| R1-2403604 |
FLS#2 for maintenance of SD-PD adaptation R18 NES |
Moderator (Huawei) |
| R1-2403605 |
Corrections on RRC parameters for R18 NES spatial/power domain adaptation |
Moderator (Huawei), Ericsson, Google, Nokia, NSB, ZTE, Sanechips, Samsung |
| R1-2403610 |
Correction of cell DTX/DRX operation terminology |
Moderator (Intel Corporation), Ericsson |
| R1-2403611 |
Correction of SRS operation during cell DRX operation |
Moderator (Intel Corporation), Huawei, HiSilicon |
| R1-2403627 |
Feature lead summary 3 on FR2-NTN discussions |
Moderator (Nokia) |
| R1-2403628 |
Summary #3 of discussion for Rel-18 NES enhancements on cell DTX/DRX mechanism |
Moderator (Intel Corporation) |
| R1-2403629 |
Summary #4 of discussion for Rel-18 NES enhancements on cell DTX/DRX mechanism |
Moderator (Intel Corporation) |
| R1-2403645 |
Draft Reply LS on 2-step RACH for eRedCap |
Ericsson |
| R1-2403646 |
Reply LS on 2-step RACH for eRedCap |
RAN1, Ericsson |
| R1-2403647 |
FL summary #3 for Rel-18 NR eRedCap maintenance |
Moderator (Ericsson) |
| R1-2403653 |
Session notes for 8.4 (Maintenance on other Rel-18 work items - Mobility Enhancement) |
Ad-Hoc Chair (CMCC) |
| R1-2403654 |
Session notes for 8.4 (Maintenance on other Rel-18 work items - Coverage Enhancement) |
Ad-Hoc Chair (CMCC) |
| R1-2403655 |
Session notes for 8.4 (Maintenance on other Rel-18 work items – Network Controlled Repeater) |
Ad-Hoc Chair (CMCC) |
| R1-2403656 |
Session notes for 8.4 Maintenance on other Rel-18 work items - IoT NTN |
Ad-Hoc Chair (Huawei) |
| R1-2403657 |
Session notes for 8.4 Maintenance on other Rel-18 work items - NR NTN |
Ad-Hoc Chair (Huawei) |
| R1-2403658 |
Session notes for 8.4 (Maintenance on other Rel-18 work items - RedCap) |
Ad-Hoc Chair (CMCC) |
| R1-2403659 |
Session notes for 8.4 Maintenance on other Rel-18 work items - Sidelink |
Ad-Hoc Chair (Huawei) |
| R1-2403660 |
Session notes for 8.4 Maintenance on other Rel-18 work items - MBS |
Ad-Hoc Chair (Huawei) |
| R1-2403661 |
Session notes for 8.4 (Maintenance on other Rel-18 work items - TEI) |
Ad-Hoc Chair (CMCC) |
| R1-2403667 |
Correction on sidelink starting symbol index for indications of UL slots in PSBCH in SL-U |
Moderator (Huawei), Sharp, vivo, Samsung |
| R1-2403668 |
Correction on description of NnonSL slots in SL-U |
Moderator (Huawei), Sharp, vivo, Samsung |
| R1-2403669 |
Correction on TRIV/FRIV resource indication of SL-U |
Moderator (Huawei), CATT, CICTCI, vivo |
| R1-2403670 |
Correction on determination of starting RB set for PSSCH |
Moderator (Huawei), Sharp, vivo, OPPO, Samsung |
| R1-2403671 |
Correction on contiguous RB based resource allocation |
Moderator (Huawei), Sharp, vivo, Samsung |
| R1-2403672 |
Correction on OFDM symbol location for PSFCH transmission in SL-U |
Moderator (Huawei), Sharp, vivo, Samsung |
| R1-2403673 |
Correction on PSFCH Power Control |
Moderator (Huawei), Samsung, CATT, CICTCI, NEC, vivo, OPPO |
| R1-2403674 |
FL summary#4 for AI 8.4 SL-U physical channel design framework |
Moderator (Huawei) |
| R1-2403680 |
FL summary 3 of Maintenance on Further NR Mobility Enhancements |
Moderator (Fujitsu) |
| R1-2403681 |
Final FL summary of Maintenance on Further NR Mobility Enhancements |
Moderator (Fujitsu) |
| R1-2403682 |
draft LS on the identification of the power control parameters after LTM cell switch |
Fujitsu |
| R1-2403683 |
LS on the identification of the power control parameters after LTM cell switch |
RAN1, Fujitsu |
| R1-2403684 |
Correction on prioritizations for transmission power reductions in LTM |
Moderator (Fujitsu), ZTE, Nokia, Ericsson, Huawei, HiSilicon, vivo, Lenovo |
| R1-2403685 |
Correction on RACH procedure triggered by LTM cell switch |
Moderator (Fujitsu), Google, ZTE, Nokia, Ericsson, Huawei, HiSilicon, vivo, Lenovo |
| R1-2403686 |
FL Summary #3: Maintenance on Rel-18 NR NTN |
Moderator (Thales) |
| R1-2403687 |
Draft CR on correction on timing of first Msg3 repetition |
Moderator (Thales) |
| R1-2403688 |
Draft CR on application time of Cell DRX in NTN |
Moderator (Thales) |
| R1-2403693 |
Draft CR for TS 38.214 for introduction of FR2-NTN |
Moderator (Nokia), NTT DOCOMO, INC. |
| R1-2403708 |
Correction on TCI state applied for CORESET 0 in LTM |
Moderator (Fujitsu), ZTE, Nokia, Ericsson, Huawei, HiSilicon, vivo, Lenovo |
| R1-2403709 |
Correction on QCL assumption after LTM cell switch command |
Moderator (Fujitsu), ZTE, Nokia, Ericsson, Huawei, HiSilicon, vivo, Lenovo |
| R1-2403710 |
Correction on PRACH collision handling in LTM |
Moderator (Fujitsu), ZTE, Nokia, Ericsson, Huawei, HiSilicon, vivo, Lenovo |
| R1-2403711 |
Correction on UL/SUL field in DCI format 1_0 in LTM |
Moderator (Fujitsu), Google, ZTE, Nokia, Ericsson, Huawei, HiSilicon, vivo, Lenovo |
| R1-2403720 |
Feature lead summary #2 of AI 8.4 maintenance of Release 18 IoT NTN |
Moderator (MediaTek) |
| R1-2403725 |
Draft CR on correction on timing of first Msg3 repetition |
Moderator (Thales) |
| R1-2403727 |
Correction on PSFCH Power Control |
Moderator (Huawei), Samsung, CATT, CICTCI, NEC, vivo, OPPO, Apple |
| R1-2403730 |
FL Summary #2 of maintenance on further NR coverage enhancements |
Moderator (China Telecom) |
| R1-2403735 |
Correction of CG bundle, SRS, and SPS PDSCH overlapping with cell DTX/DRX operation |
Moderator (Intel Corporation), Intel Corporation, Qualcomm |
| R1-2403736 |
Correction of power consistency and phase continuity during cell DRX operation |
Moderator (Intel Corporation), Qualcomm, Apple |
| R1-2403737 |
Draft CR for TS 38.214 for introduction of FR2-NTN |
Moderator (Nokia), NTT DOCOMO, INC. |
| R1-2403738 |
Feature lead summary #3 of AI 8.4 maintenance of Release 18 IoT NTN |
Moderator (MediaTek) |
| R1-2403739 |
Draft CR for 38.211 on Introduction of FR2-NTN |
Ericsson, Thales, CATT, ESA, Eutelsat Group, Lockheed Martin, Inmarsat, Sharp |
| R1-2403754 |
CR on correction on timing of first Msg3 repetition |
Moderator (Thales), vivo, Ericsson, Samsung |
| R1-2403790 |
Draft CR for TS 38.211 for introduction of FR2-NTN |
Moderator (Nokia), NTT DOCOMO, INC. |
| R1-2403791 |
Draft CR for 38.211 on Introduction of FR2-NTN |
Moderator (Nokia), Ericsson, Thales, CATT, ESA, Eutelsat Group, Lockheed Martin, Inmarsat, Sharp |
| R1-2403792 |
Email discussion on FR2-NTN PRACH Configuration Table |
Moderator (Nokia) |
| 8.5 |
UE Features |
|
| R1-2403703 |
Updated RAN1 UE features list for Rel-18 NR after RAN1 #116bis |
Moderators (AT&T, NTT DOCOMO, INC.) |
| R1-2403704 |
Draft LS on updated Rel-18 RAN1 UE features lists for NR after RAN1#116bis |
Moderators (AT&T, NTT DOCOMO, INC.) |
| R1-2403705 |
LS on Rel-18 RAN1 UE features list for NR after RAN1#116bis |
RAN1, (AT&T, NTT DOCOMO, INC.) |
| R1-2403747 |
Summary of discussion on UE features for MBS |
Moderator (NTT DOCOMO, INC.) |
| R1-2403748 |
Session Notes of AI 8.5 |
Ad-Hoc Chair (NTT DOCOMO, INC.) |
| 8.5.1 |
UE features for NR sidelink evolution (NR_SL_enh2) |
|
| R1-2402022 |
UE features for NR sidelink evolution |
Huawei, HiSilicon |
| R1-2402227 |
Discussion on UE features for NR SL evoluation |
vivo |
| R1-2402313 |
UE features list for Rel-18 NR sidelink evolution WI |
OPPO, Huawei, HiSilicon, LG Electronics |
| R1-2402364 |
Remaining issues on UE features for NR sidelink evolution |
CATT, CICTCI |
| R1-2402451 |
UE features for NR sidelink evolution |
Samsung |
| R1-2402603 |
Remaining issues of NR sidelink evolution UE features |
Nokia |
| R1-2402645 |
Maintenance on UE features for NR sidelink evolution |
Xiaomi |
| R1-2402776 |
UE features for NR sidelink evolution |
ZTE, Sanechips |
| R1-2402867 |
UE Features for Rel-18 NR Sidelink Evolution |
Apple |
| R1-2403179 |
UE Features for Sidelink Evolution |
Qualcomm Incorporated |
| R1-2403229 |
Discussion on UE features for NR SL evolution |
NTT DOCOMO, INC. |
| R1-2403298 |
Discussion on UE features for Rel-18 NR sidelink evolution |
Sharp |
| R1-2403430 |
Summary of discussion on UE features for NR sidelink evolution |
Moderator (NTT DOCOMO, INC.) |
| R1-2403614 |
Summary#2 of discussion on UE features for NR sidelink evolution |
Moderator (NTT DOCOMO, INC.) |
| R1-2403700 |
Session Notes of AI 8.5.1 |
Ad-Hoc Chair (NTT DOCOMO, INC.) |
| 8.5.2 |
UE features for other Rel-18 work items (Topics A: NR_MC_enh, NR_redcap_enh, NR_XR_enh, NR_cov_enh2, NR_FR1_lessthan_5MHz_BW, NR_DSS_enh, TEI) |
|
| R1-2402007 |
UE features for other Rel-18 WIs (Topics A) |
Huawei, HiSilicon |
| R1-2402164 |
Discussion on UE feature topics A |
ZTE |
| R1-2402228 |
Discussion on UE features for NR multi-carrier enhancement |
vivo |
| R1-2402314 |
Discussion on UE features for multi-carrier enhancement |
OPPO |
| R1-2402452 |
UE features for other Rel-18 work items (Topic A) |
Samsung |
| R1-2402592 |
Rel-18 UE features topics set A |
Ericsson |
| R1-2402598 |
A joint proposal on UE features for NR support for dedicated spectrum less than 5 MHz for FR1 |
Nokia, Ericsson, Huawei, Qualcomm |
| R1-2402604 |
Remaining issues of UE Features for Other Topics A (MCenh, eRedCap, NRenh, covEnh2, sub5MHz, eDSS, TEI) |
Nokia |
| R1-2402646 |
Discussion on UE features for eRedCap |
Xiaomi |
| R1-2403180 |
UE features for other Rel-18 work items (Topics A) |
Qualcomm Incorporated |
| R1-2403230 |
Discussion on UE features for other Rel-18 work items (Topics A) |
NTT DOCOMO, INC. |
| R1-2403431 |
Summary of discussion on UE features for MC enhancements |
Moderator (NTT DOCOMO, INC.) |
| R1-2403432 |
Summary of discussion on UE features for eRedCap |
Moderator (NTT DOCOMO, INC.) |
| R1-2403433 |
Summary of discussion on UE features for XR enhancements |
Moderator (NTT DOCOMO, INC.) |
| R1-2403434 |
Summary of discussion on UE features for eDSS |
Moderator (NTT DOCOMO, INC.) |
| R1-2403435 |
Summary of discussion on UE features for dedicated spectrum less than 5MHz |
Moderator (NTT DOCOMO, INC.) |
| R1-2403436 |
Summary of discussion on UE features for TEIs |
Moderator (NTT DOCOMO, INC.) |
| R1-2403694 |
Summary#2 of discussion on UE features for MC enhancements |
Moderator (NTT DOCOMO, INC.) |
| R1-2403695 |
Summary#2 of discussion on UE features for eRedCap |
Moderator (NTT DOCOMO, INC.) |
| R1-2403696 |
Summary#2 of discussion on UE features for XR enhancements |
Moderator (NTT DOCOMO, INC.) |
| R1-2403697 |
Summary#2 of discussion on UE features for eDSS |
Moderator (NTT DOCOMO, INC.) |
| R1-2403698 |
Summary#2 of discussion on UE features for dedicated spectrum less than 5MHz |
Moderator (NTT DOCOMO, INC.) |
| R1-2403699 |
Summary#2 of discussion on UE features for TEIs |
Moderator (NTT DOCOMO, INC.) |
| R1-2403701 |
Session Notes of AI 8.5.2 |
Ad-Hoc Chair (NTT DOCOMO, INC.) |
| 8.5.3 |
UE features for other Rel-18 work items (Topics B: NR_MIMO_evo_DL_UL, NR_pos_enh2, Netw_Energy_NR, NR_Mob_enh2, NR_netcon_repeater, IoT_NTN_enh, NR_NTN_enh, NR_BWP_wor) |
|
| R1-2402008 |
UE features for other Rel-18 WIs (Topics B) |
Huawei, HiSilicon |
| R1-2402143 |
UE features for Rel-18 Work Items (Topics B) |
Intel Corporation |
| R1-2402229 |
Discussion on UE features for Topic B |
vivo |
| R1-2402315 |
UE features for other Rel-18 work items (Topics B) |
OPPO |
| R1-2402365 |
Remaining issues on UE features for MIMO and Positioning |
CATT |
| R1-2402453 |
UE features for other Rel-18 work items (Topic B) |
Samsung |
| R1-2402552 |
Discussion on UE features for NR ATG |
CMCC |
| R1-2402605 |
Remaining issues of UE Features for Other Topics B (MIMO, FePos, NES, MobEnh, NCR, IoT-NTN, NR-NTN, BWP_wor) |
Nokia, Nokia Shanghai Bell |
| R1-2402647 |
Discussion on UE features for NR MIMO evolution |
Xiaomi |
| R1-2402702 |
UE features for other Rel-18 work items (Topics B) |
ZTE Corporation |
| R1-2402868 |
Views on UE features for other Rel-18 work items (Topics B) |
Apple |
| R1-2402955 |
UE features for other Rel-18 work items (Topics B) |
MediaTek |
| R1-2403116 |
Discussion on UE features for NES |
LG Electronics |
| R1-2403181 |
UE features for other Rel-18 work items (Topics B) |
Qualcomm Incorporated |
| R1-2403231 |
Discussion on UE features for other Rel-18 work items (Topics B) |
NTT DOCOMO, INC. |
| R1-2403271 |
Rel-18 UE features topics set B |
Ericsson |
| R1-2403409 |
Views on UE features for other Rel-18 work items (Topics B) |
Apple |
| R1-2403571 |
Summary of UE features for other Rel-18 work items (Topics B) |
Moderator (AT&T) |
| R1-2403615 |
Summary#2 of UE features for other Rel-18 work items (Topics B) |
Moderator (AT&T) |
| R1-2403702 |
Session Notes of AI 8.5.3 |
Ad-Hoc Chair (NTT DOCOMO, INC.) |
| R1-2403763 |
Final summary of UE features for other Rel-18 work items (Topics B) |
Moderator (AT&T) |
| 9 |
Release 19 |
|
| R1-2402648 |
Discussion on the CR drafting for ISAC and 7-24 GHz |
Xiaomi, AT&T, Intel, ZTE, Samsung |
| R1-2403780 |
On the CR drafting for ISAC and 7-24 GHz |
Xiaomi, AT&T, Intel, ZTE, Samsung |
| 9.1 |
Artificial Intelligence (AI)/Machine Learning (ML) for NR Air Interface (NR_AIML_Air) |
|
| R1-2403662 |
Session notes for 9.1 (AI/ML for NR Air Interface) |
Ad-Hoc Chair (CMCC) |
| 9.1.1 |
Specification support for beam management |
|
| R1-2402023 |
Discussion on AI/ML for beam management |
Huawei, HiSilicon |
| R1-2402054 |
Discussion on specification support for AI/ML-based beam management |
FUTUREWEI |
| R1-2402056 |
AI/ML for beam management |
Ericsson |
| R1-2402094 |
Discussion on AIML for beam management |
Spreadtrum Communications |
| R1-2402144 |
Specification support for AI/ML for beam management |
Intel Corporation |
| R1-2402230 |
Specification support for beam management |
vivo |
| R1-2402263 |
Discussion on specification support for AI/ML beam management |
ZTE |
| R1-2402276 |
AI/ML based Beam Management |
Google |
| R1-2402316 |
On specification for AI/ML-based beam management |
OPPO |
| R1-2402366 |
Specification support for AI/ML-based beam management |
CATT |
| R1-2402491 |
Discussion for supporting AI/ML based beam management |
Samsung |
| R1-2402553 |
Discussion on specification support for beam management |
CMCC |
| R1-2402609 |
Discussion on AI/ML for beam management |
InterDigital, Inc. |
| R1-2402626 |
Discussion on specification support for beam management |
Panasonic |
| R1-2402628 |
Discussions on AI/ML for beam management |
LG Electronics |
| R1-2402649 |
Specification support for beam management |
Xiaomi |
| R1-2402730 |
Discussions on AIML for beam management |
New H3C Technologies Co., Ltd. |
| R1-2402756 |
Discussion on specification support for beam management |
NEC |
| R1-2402786 |
Discussion on specification support on AI/ML for beam management |
Fujitsu |
| R1-2402846 |
Specification support for AI-enabled beam management |
NVIDIA |
| R1-2402869 |
On AI/ML for beam management |
Apple |
| R1-2402918 |
AI/ML specification support for beam management |
Lenovo |
| R1-2402939 |
Discussion on specification support for AI/ML-based beam management |
MediaTek |
| R1-2402957 |
Discussions on AI/ML for beam management |
Sony |
| R1-2402996 |
AI/ML for Beam Management |
Nokia |
| R1-2403006 |
Specification support for AI/ML beam management |
ITL |
| R1-2403011 |
Discussion on specification support for beam management |
ETRI |
| R1-2403036 |
Discussion on AI/ML beam management |
TCL |
| R1-2403041 |
Specification support for beam management |
Fraunhofer HHI, Fraunhofer IIS |
| R1-2403051 |
Discussion on Specification Support for Beam Management |
CEWiT |
| R1-2403131 |
Discussion on AI/ML based beam management |
KT Corp. |
| R1-2403141 |
Specification support for beam management |
KDDI Corporation |
| R1-2403157 |
Discussions on AI/ML for beam management |
CAICT |
| R1-2403182 |
Specification support for AI-ML-based beam management |
Qualcomm Incorporated |
| R1-2403232 |
Discussion on AI/ML for beam management |
NTT DOCOMO, INC. |
| R1-2403299 |
Discussions on specification support for beam management |
Sharp |
| R1-2403367 |
Discussions on Specification Support of AI/ML for Beam Management |
Indian Institute of Tech (M), IIT Kanpur |
| R1-2403563 |
FL summary #0 for AI/ML in beam management |
Moderator (Samsung) |
| R1-2403568 |
FL summary #1 for AI/ML in beam management |
Moderator (Samsung) |
| R1-2403569 |
FL summary #2 for AI/ML in beam management |
Moderator (Samsung) |
| R1-2403570 |
FL summary #3 for AI/ML in beam management |
Moderator (Samsung) |
| R1-2403755 |
FL summary #4 for AI/ML in beam management |
Moderator (Samsung) |
| R1-2403756 |
FL summary #5 for AI/ML in beam management |
Moderator (Samsung) |
| 9.1.2 |
Specification support for positioning accuracy enhancement |
|
| R1-2401984 |
AI/ML for Positioning Accuracy Enhancement |
Ericsson Inc. |
| R1-2402024 |
Discussion on AI/ML for positioning accuracy enhancement |
Huawei, HiSilicon |
| R1-2402039 |
AI/ML positioning accuracy enhancement |
Fraunhofer IIS, Fraunhofer HHI |
| R1-2402145 |
Specification support for AI/ML for positioning accuracy enhancement |
Intel Corporation |
| R1-2402231 |
Specification support for positioning accuracy enhancement |
vivo |
| R1-2402264 |
Discussion on specification support for AI/ML positioning accuracy enhancement |
ZTE, Pengcheng laboratory |
| R1-2402269 |
Discussion on specification support for positioning accuracy enhancement |
TCL |
| R1-2402277 |
AI/ML based Positioning |
Google |
| R1-2402317 |
On specification for AI/ML-based positioning accuracy enhancements |
OPPO |
| R1-2402367 |
Specification support for AI/ML-based positioning accuracy enhancement |
CATT, CICTCI |
| R1-2402492 |
Discussion for supporting AI/ML based positioning accuracy enhancement |
Samsung |
| R1-2402554 |
Discussion on specification support for positioning accuracy enhancement |
CMCC |
| R1-2402650 |
Discussion on AI/ML-based positioning accuracy enhancement |
Xiaomi |
| R1-2402764 |
Discussion on specification support for AI/ML based positioning accuracy enhancement |
NEC |
| R1-2402787 |
Discussion on specification support for AI/ML positioning accuracy enhancement |
Fujitsu |
| R1-2402799 |
Design for AI/ML based positioning |
MediaTek Korea Inc. |
| R1-2402847 |
Specification support for AI-enabled positioning |
NVIDIA |
| R1-2402870 |
On AI/ML for Positioning Accuracy Enhancement |
Apple |
| R1-2402913 |
Discussion on support for AIML positioning |
InterDigital, Inc. |
| R1-2402919 |
Specification impacts for Enhanced Positioning |
Lenovo |
| R1-2402958 |
Discussion on supporting AI/ML for positioning |
Sony |
| R1-2402997 |
AI/ML for Positioning Accuracy Enhancement |
Nokia |
| R1-2403012 |
Discussion on specification support for positioning accuracy enhancement |
ETRI |
| R1-2403035 |
Discussion on specification support for positioning accuracy enhancement |
TCL |
| R1-2403052 |
Discussion on specification support for AI/ML Positioning Accuracy enhancement |
CEWiT |
| R1-2403183 |
Specification support for AI-ML-based positioning accuracy enhancement |
Qualcomm Incorporated |
| R1-2403233 |
Discussion on AI/ML for positioning accuracy enhancement |
NTT DOCOMO, INC. |
| R1-2403300 |
Discussions on specification support for AI/ML based positioning accuracy enhancements |
Sharp |
| R1-2403458 |
Summary #1 of specification support for positioning accuracy enhancement |
Moderator (Ericsson) |
| R1-2403459 |
Summary #2 of specification support for positioning accuracy enhancement |
Moderator (Ericsson) |
| R1-2403460 |
Summary #3 of specification support for positioning accuracy enhancement |
Moderator (Ericsson) |
| R1-2403461 |
Summary #4 of specification support for positioning accuracy enhancement |
Moderator (Ericsson) |
| R1-2403462 |
Summary #5 of specification support for positioning accuracy enhancement |
Moderator (Ericsson) |
| R1-2403740 |
Summary #6 of specification support for positioning accuracy enhancement |
Moderator (Ericsson) |
| R1-2403741 |
Final summary of specification support for positioning accuracy enhancement |
Moderator (Ericsson) |
| 9.1.3.1 |
CSI prediction |
|
| R1-2402025 |
Discussion on AI/ML for CSI prediction |
Huawei, HiSilicon |
| R1-2402095 |
Discussion on AIML for CSI prediction |
Spreadtrum Communications |
| R1-2402146 |
AI/ML for CSI prediction |
Intel Corporation |
| R1-2402232 |
Discussion on CSI prediction |
vivo |
| R1-2402265 |
Discussion on study for AI/ML CSI prediction |
ZTE |
| R1-2402278 |
AI/ML based CSI Prediction |
Google |
| R1-2402318 |
Additional study on AI/ML-based CSI prediction |
OPPO |
| R1-2402368 |
Additional study on AI/ML-based CSI prediction |
CATT |
| R1-2402454 |
Discussion for further study on AI/ML-based CSI prediction |
Samsung |
| R1-2402494 |
AI/ML for CSI prediction |
Ericsson |
| R1-2402505 |
Discussion on AI/ML-based CSI prediction |
China Telecom |
| R1-2402535 |
AI/ML for CSI prediction |
Mavenir |
| R1-2402555 |
Discussion on AI/ML for CSI prediction |
CMCC |
| R1-2402629 |
Study on CSI prediction |
LG Electronics |
| R1-2402651 |
Discussion on one side AI/ML model based CSI prediction |
Xiaomi |
| R1-2402749 |
Discussion on AI/ML for CSI prediction |
Panasonic |
| R1-2402765 |
Discussion on CSI prediction |
NEC |
| R1-2402788 |
Discussion on CSI prediction with AI/ML |
Fujitsu |
| R1-2402842 |
Discussion on AI/ML-based CSI prediction |
InterDigital, Inc. |
| R1-2402848 |
Additional study on AI-enabled CSI prediction |
NVIDIA |
| R1-2402871 |
Discussion on AI based CSI prediction |
Apple |
| R1-2402920 |
On AI/ML for CSI prediction |
Lenovo |
| R1-2402959 |
Discussions on cell/site-specific CSI prediction |
Sony |
| R1-2402998 |
AI/ML for CSI Prediction |
Nokia |
| R1-2403053 |
Discussion on AI/ML for CSI Prediction |
CEWiT |
| R1-2403075 |
Additional Study on AI/ML for CSI Prediction |
MediaTek |
| R1-2403096 |
Discussion on AI/ML for CSI prediction |
SK Telecom |
| R1-2403146 |
Discussion on AI/ML for CSI prediction |
AT&T |
| R1-2403184 |
Additional study on CSI prediction |
Qualcomm Incorporated |
| R1-2403234 |
Discussion on AI/ML for CSI prediction |
NTT DOCOMO, INC. |
| R1-2403379 |
Discussion on study of AI/ML for CSI prediction |
IIT Kanpur, Indian Institute of Tech (M) |
| R1-2403481 |
Summary #1 of CSI prediction |
Moderator (LG Electronics) |
| R1-2403482 |
Summary #2 of CSI prediction |
Moderator (LG Electronics) |
| R1-2403483 |
Summary #3 of CSI prediction |
Moderator (LG Electronics) |
| R1-2403484 |
Summary #4 of CSI prediction |
Moderator (LG Electronics) |
| 9.1.3.2 |
CSI compression |
|
| R1-2402026 |
Discussion on AI/ML for CSI compression |
Huawei, HiSilicon |
| R1-2402053 |
Discussion on improving trade-off between performance and complexity/overhead for AI/ML-based temporal-domain CSI feedback compression. |
FUTUREWEI |
| R1-2402096 |
Discussion on AIML for CSI compression |
Spreadtrum Communications |
| R1-2402147 |
AI/ML for CSI compression |
Intel Corporation |
| R1-2402233 |
Discussion on CSI compression |
vivo |
| R1-2402266 |
Discussion on study for AI/ML CSI compression |
ZTE |
| R1-2402279 |
AI/ML based CSI Compression |
Google |
| R1-2402319 |
Additional study on AI/ML-based CSI compression |
OPPO |
| R1-2402369 |
Additional study on AI/ML-based CSI compression |
CATT |
| R1-2402455 |
Discussion for further study on AI/ML-based CSI compression |
Samsung |
| R1-2402495 |
AI/ML for CSI compression |
Ericsson |
| R1-2402506 |
Discussion on AI/ML-based CSI compression |
China Telecom |
| R1-2402526 |
Discussion on CSI compression for AI/ML |
BJTU |
| R1-2402556 |
Discussion on AI/ML for CSI compression |
CMCC |
| R1-2402630 |
Study on CSI compression |
LG Electronics |
| R1-2402652 |
Discussion on two-sided AI/ML model based CSI compression |
Xiaomi |
| R1-2402750 |
Discussion on AI/ML for CSI compression |
Panasonic |
| R1-2402766 |
Discussion on CSI compression |
NEC |
| R1-2402789 |
Discussion on CSI compression with AI/ML |
Fujitsu |
| R1-2402843 |
Discussion on AI/ML-based CSI compression |
InterDigital, Inc. |
| R1-2402849 |
Additional study on AI-enabled CSI compression |
NVIDIA |
| R1-2402872 |
Discussion on AI based CSI compression |
Apple |
| R1-2402921 |
On AI/ML for CSI compression |
Lenovo |
| R1-2402960 |
Discussion on CSI compression |
Sony |
| R1-2402999 |
AI/ML for CSI Compression |
Nokia |
| R1-2403013 |
Discussion on AI/ML for CSI compression |
ETRI |
| R1-2403054 |
Discussion on AI/ML for CSI Compression |
CEWiT |
| R1-2403076 |
Additional Study on AI/ML for CSI Compression |
MediaTek |
| R1-2403100 |
Discussion on AI/ML for CSI compression |
SK Telecom |
| R1-2403147 |
Discussion on AI/ML for CSI compression |
AT&T |
| R1-2403158 |
Discussions on AI/ML for CSI feedback |
CAICT |
| R1-2403185 |
Additional study on CSI compression |
Qualcomm Incorporated |
| R1-2403235 |
Discussion on AI/ML for CSI compression |
NTT DOCOMO, INC. |
| R1-2403279 |
AI/ML based CSI compression |
ITL |
| R1-2403336 |
Discussion on the AI/ML for CSI Compression |
Fraunhofer IIS, Fraunhofer HHI |
| R1-2403380 |
Discussion on study of AI/ML for CSI compression |
IIT Kanpur, Indian Institute of Tech (M) |
| R1-2403381 |
Discussion on Additional Study of AI/ML for CSI Compression |
Indian Institute of Tech (M), IIT Kanpur |
| R1-2403500 |
Summary#1 of Additional study on AI/ML for NR air interface: CSI compression |
Moderator (Qualcomm) |
| R1-2403501 |
Summary#2 of Additional study on AI/ML for NR air interface: CSI compression |
Moderator (Qualcomm) |
| R1-2403502 |
Summary#3 of Additional study on AI/ML for NR air interface: CSI compression |
Moderator (Qualcomm) |
| R1-2403503 |
Summary#4 of Additional study on AI/ML for NR air interface: CSI compression |
Moderator (Qualcomm) |
| R1-2403504 |
Summary#5 of Additional study on AI/ML for NR air interface: CSI compression |
Moderator (Qualcomm) |
| R1-2403505 |
Final summary of Additional study on AI/ML for NR air interface: CSI compression |
Moderator (Qualcomm) |
| 9.1.3.3 |
Other aspects of AI/ML model and data |
|
| R1-2402027 |
Discussion on other aspects of the additional study for AI/ML |
Huawei, HiSilicon |
| R1-2402052 |
Discussion on other aspects of AI/ML model and data on AI/ML for NR air-interface |
FUTUREWEI |
| R1-2402057 |
Discussion on other aspects of AI/ML |
Ericsson |
| R1-2402097 |
Discussion on other aspects of AI/ML model and data |
Spreadtrum Communications |
| R1-2402148 |
Other study aspects of AI/ML for air interface |
Intel Corporation |
| R1-2402234 |
Other aspects of AI/ML model and data |
vivo |
| R1-2402267 |
Discussion on study for other aspects of AI/ML model and data |
ZTE |
| R1-2402280 |
AI/ML Model and Data |
Google |
| R1-2402320 |
Additional study on other aspects of AI/ML model and data |
OPPO |
| R1-2402370 |
Additional study on other aspects of AI/ML model and data |
CATT, CICTCI |
| R1-2402456 |
Discussion for further study on other aspects of AI/ML model and data |
Samsung |
| R1-2402557 |
Discussion on other aspects of AI/ML model and data |
CMCC |
| R1-2402631 |
Discussion on other aspects of AI/ML model and data |
LG Electronics |
| R1-2402653 |
Further study on AI/ML model and data |
Xiaomi |
| R1-2402695 |
Discussion on other aspects for AI/ML for air interface |
Panasonic |
| R1-2402757 |
Discussion on other aspects of AI/ML model and data |
NEC |
| R1-2402790 |
Discussion on other aspects of AI/ML model and data |
Fujitsu |
| R1-2402800 |
View on AI/ML model and data |
MediaTek Korea Inc. |
| R1-2402801 |
Discussion on other aspects of AI/ML model and data |
Continental Automotive |
| R1-2402844 |
Discussion on other aspects of AI/ML model and data |
InterDigital, Inc. |
| R1-2402850 |
Additional study on other aspects of AI model and data |
NVIDIA |
| R1-2402873 |
Discussion on other aspects of AI/ML model and data |
Apple |
| R1-2402922 |
On aspects of AI/ML model and data framework |
Lenovo |
| R1-2403000 |
Other Aspects of AI/ML Model and Data |
Nokia |
| R1-2403014 |
Discussion on other aspects of AI/ML model and data |
ETRI |
| R1-2403148 |
Other Aspects of AI/ML framework |
AT&T |
| R1-2403186 |
Other aspects of AI/ML model and data |
Qualcomm Incorporated |
| R1-2403236 |
Discussion on other aspects of AI/ML model and data |
NTT DOCOMO, INC. |
| R1-2403489 |
Summary #1 for other aspects of AI/ML model and data |
Moderator (OPPO) |
| R1-2403490 |
Summary #2 for other aspects of AI/ML model and data |
Moderator (OPPO) |
| R1-2403491 |
Summary #3 for other aspects of AI/ML model and data |
Moderator (OPPO) |
| R1-2403492 |
Summary #4 for other aspects of AI/ML model and data |
Moderator (OPPO) |
| R1-2403493 |
Summary #5 for other aspects of AI/ML model and data |
Moderator (OPPO) |
| 9.2.1 |
Enhancements for UE-initiated/event-driven beam management |
|
| R1-2402017 |
On UE initiated/event-driven beam management |
Huawei, HiSilicon |
| R1-2402051 |
Enhancements for UE-initiated/event-driven beam management |
FUTUREWEI |
| R1-2402063 |
Discussion on enhancements for UE-initiated/event-driven beam management |
ZTE |
| R1-2402079 |
Rel-19 UE/Event-Driven Beam Management |
InterDigital, Inc. |
| R1-2402098 |
Discussion on UE-initiated/event-driven beam management |
Spreadtrum Communications |
| R1-2402138 |
Enhancements for event driven beam management |
Intel Corporation |
| R1-2402155 |
Enhancements for UE-initiated/event-driven beam management |
MediaTek Inc. |
| R1-2402235 |
Discussion on UE-initiated/event-driven beam management |
vivo |
| R1-2402321 |
Discussions on UE-initiated/event-driven beam management |
OPPO |
| R1-2402376 |
Discussion on UE-initiated/event-driven beam management |
CATT |
| R1-2402457 |
Views on Rel-19 UE-initiated/event-driven beam management |
Samsung |
| R1-2402496 |
Enhancements for UE-initiated/event-driven beam management |
Lenovo |
| R1-2402529 |
Discussion on enhancements for UE-initiated/event-driven beam management |
Langbo |
| R1-2402558 |
Discussion on enhancements for UE-initiated/event-driven beam management |
CMCC |
| R1-2402632 |
UE-initiated beam management |
LG Electronics |
| R1-2402659 |
Enhancements for UE-initiated/event-driven beam management |
Xiaomi |
| R1-2402684 |
Enhancements for UE-initiated/event-driven beam management |
Transsion Holdings |
| R1-2402711 |
Offline summary for Rel-19 MIMO UEIBM |
Moderator (ZTE) |
| R1-2402712 |
Moderator Summary #1 on UE-initiated/event-driven beam management |
Moderator (ZTE) |
| R1-2402713 |
Moderator Summary #2 on UE-initiated/event-driven beam management |
Moderator (ZTE) |
| R1-2402714 |
Moderator Summary #3 on UE-initiated/event-driven beam management |
Moderator (ZTE) |
| R1-2402718 |
Discussion on UE initiated report |
ASUSTeK |
| R1-2402721 |
Discussion on UE-initiated/event-driven beam management |
Honor |
| R1-2402758 |
Discussion on enhancements for UE-initiated or event-driven beam management |
NEC |
| R1-2402791 |
Discussion on enhancements for UE-initiated/event-driven beam management |
Fujitsu |
| R1-2402806 |
Discussion on UE-initiated/event-driven beam management |
ITRI |
| R1-2402838 |
Enhancements to facilitate UE-initiated/event-driven beam management |
Nokia |
| R1-2402874 |
Views on UE-initiated beam management |
Apple |
| R1-2402961 |
Discussion on UE initiated beam management |
Sony |
| R1-2402982 |
Enhancements for UE-initiated beam management |
Ericsson |
| R1-2403015 |
Enhancements for UE-initiated/event-driven beam management |
ETRI |
| R1-2403055 |
Enhancements for UE-initiated/event-driven beam management |
CEWiT |
| R1-2403068 |
Discussions on enhancements for UE-initiated/event-driven beam management |
Ruijie Networks Co. Ltd |
| R1-2403088 |
Discussion on enhancements for UE-initiated or event-driven beam management |
Google |
| R1-2403108 |
Enhancements for UE-initiated/event-driven beam management |
Sharp |
| R1-2403113 |
Enhancements for UE-initiated/event-driven beam management |
Panasonic |
| R1-2403187 |
UE-initiated/event-driven beam management |
Qualcomm Incorporated |
| R1-2403237 |
Discussion on enhancements for UE-initiated/event-driven beam management |
NTT DOCOMO, INC. |
| R1-2403354 |
Views on enhancements for UE-initiated/event-driven beam management. |
KDDI Corporation |
| R1-2403690 |
Summary #4 on UE-initiated/event-driven beam management |
Moderator (ZTE) |
| 9.2.2 |
CSI enhancements |
|
| R1-2402018 |
On 128 CSI-RS ports and UE reporting enhancement |
Huawei, HiSilicon |
| R1-2402064 |
Discussion on CSI enhancements |
ZTE |
| R1-2402080 |
Rel-19 Enhancements of CSI |
InterDigital, Inc. |
| R1-2402099 |
Discussion on CSI enhancements |
Spreadtrum Communications |
| R1-2402127 |
CSI Enhancements for NR MIMO Evolution |
Kyocera Corporation |
| R1-2402139 |
CSI enhancements for MIMO |
Intel Corporation |
| R1-2402156 |
CSI enhancements to support up to 128 CSI-RS ports |
MediaTek Inc. |
| R1-2402180 |
Discussion on CSI enhancements |
TCL |
| R1-2402236 |
Discussion on Rel-19 CSI enhancements |
vivo |
| R1-2402281 |
CSI Enhancement for NR MIMO |
Google |
| R1-2402322 |
CSI enhancements for Rel-19 MIMO |
OPPO |
| R1-2402377 |
Discussion on Rel-19 MIMO CSI enhancements |
CATT |
| R1-2402406 |
CSI enhancement for NR MIMO Phase 5 |
Tejas Network Limited |
| R1-2402458 |
Moderator summary for OFFLINE discussion on Rel-19 CSI enhancements |
Moderator (Samsung) |
| R1-2402459 |
Moderator summary on Rel-19 CSI enhancements |
Moderator (Samsung) |
| R1-2402460 |
Views on Rel-19 CSI enhancements |
Samsung |
| R1-2402497 |
Discussion on CSI enhancements |
Lenovo |
| R1-2402538 |
Discussion on Rel-19 CSI enhancements |
New H3C Technologies Co., Ltd. |
| R1-2402559 |
Discussion on CSI enhancements |
CMCC |
| R1-2402633 |
Discussions on CSI enhancements |
LG Electronics |
| R1-2402660 |
Discussion on CSI enhancement for up to 128 ports and CJT |
Xiaomi |
| R1-2402722 |
Discussion on CSI enhancements |
Honor |
| R1-2402767 |
Discussion on CSI enhancements |
NEC |
| R1-2402792 |
Discussion on Rel-19 CSI enhancements |
Fujitsu |
| R1-2402839 |
CSI enhancement for NR MIMO Phase 5 |
Nokia |
| R1-2402875 |
Views on R19 MIMO CSI enhancement |
Apple |
| R1-2402928 |
CSI enhancements for large antenna arrays and CJT |
Ericsson |
| R1-2402962 |
Further views on CSI enhancements |
Sony |
| R1-2403056 |
CSI Enhancements |
CEWiT |
| R1-2403109 |
CSI enhancements |
Sharp |
| R1-2403130 |
Discussion on UE reporting enhancement for CJT |
Panasonic |
| R1-2403145 |
Views on Rel-19 CSI enhancements |
AT&T |
| R1-2403188 |
CSI enhancements for >32 ports and UE-assisted CJT with non-ideal TRP synchronization |
Qualcomm Incorporated |
| R1-2403238 |
Discussion on CSI enhancements |
NTT DOCOMO, INC. |
| R1-2403327 |
CSI enhancements for Rel.19 MIMO |
Fraunhofer IIS, Fraunhofer HHI |
| R1-2403365 |
Discussion on CSI enhancements for NR MIMO Phase 5 |
KDDI Corporation |
| R1-2403424 |
Views on Rel-19 CSI enhancements |
Samsung |
| R1-2403425 |
CSI enhancements for >32 ports and UE-assisted CJT with non-ideal TRP synchronization |
Qualcomm Incorporated |
| R1-2403452 |
CSI enhancement for NR MIMO Phase 5 |
Nokia |
| R1-2403476 |
CSI enhancements for large antenna arrays and CJT |
Ericsson |
| R1-2403485 |
Views on Rel-19 CSI enhancements |
Samsung |
| R1-2403523 |
Moderator Summary#2 on Rel-19 CSI enhancements: ROUND 2 |
Moderator (Samsung) |
| R1-2403524 |
Moderator Summary for Tuesday OFFLINE session on Rel-19 CSI enhancements |
Moderator (Samsung) |
| R1-2403555 |
CSI enhancement for NR MIMO Phase 5 |
Nokia |
| R1-2403602 |
Moderator Summary#3 on Rel-19 CSI enhancements: ROUND 3 |
Moderator (Samsung) |
| R1-2403603 |
Moderator Summary for Wednesday OFFLINE session on Rel-19 CSI enhancements |
Moderator (Samsung) |
| R1-2403641 |
Moderator Summary#4 on Rel-19 CSI enhancements: ROUND 4 |
Moderator (Samsung) |
| R1-2403642 |
Moderator Summary for Thursday OFFLINE session on Rel-19 CSI enhancements |
Moderator (Samsung) |
| R1-2403649 |
DRAFT LS to RAN2 on CBSR for Rel-19 MIMO |
Samsung |
| R1-2403650 |
LS to RAN2 on CBSR for Rel-19 MIMO |
RAN1, Samsung |
| 9.2.3 |
Support for 3-antenna-port codebook-based transmissions |
|
| R1-2402019 |
On codebook for 3-antenna-port UL transmission |
Huawei, HiSilicon |
| R1-2402065 |
Discussion on 3-antenna-port codebook-based transmissions |
ZTE |
| R1-2402081 |
Rel-19 CB-based UL for 3TX UE |
InterDigital, Inc. |
| R1-2402083 |
FL Summary Support for 3TX CB-based Uplink; Preparatory |
Moderator (InterDigital, Inc.) |
| R1-2402084 |
FL Summary Support for 3TX CB-based Uplink; First Round |
Moderator (InterDigital, Inc.) |
| R1-2402085 |
FL Summary Support for 3TX CB-based Uplink; Second Round |
Moderator (InterDigital, Inc.) |
| R1-2402086 |
Recommended Direction on 3TX CB-based Uplink in RAN1#117 |
Moderator (InterDigital, Inc.) |
| R1-2402100 |
Discussion on 3-antenna-port codebook-based transmissions |
Spreadtrum Communications |
| R1-2402140 |
Support for 3Tx UL MIMO |
Intel Corporation |
| R1-2402157 |
Support for 3-antenna-port codebook-based transmissions |
MediaTek Inc. |
| R1-2402179 |
Support for 3-antenna-port codebook-based transmissions |
TCL |
| R1-2402237 |
Discussion on 3-antenna-port codebook-based uplink transmissions |
vivo |
| R1-2402282 |
Uplink 3 Port Codebook based Transmission |
Google |
| R1-2402323 |
Discussion on 3-antenna-port codebook-based transmissions |
OPPO |
| R1-2402378 |
Discussion on support for 3-antenna-port codebook-based transmissions |
CATT |
| R1-2402461 |
Views on Rel-19 3-antenna-port codebook-based transmissions |
Samsung |
| R1-2402498 |
Support for 3-antenna-port codebook-based transmissions |
Lenovo |
| R1-2402530 |
Discussion on 3-antenna-port codebook-based transmissions |
Langbo |
| R1-2402560 |
Discussion on support for 3-antenna-port codebook-based transmissions |
CMCC |
| R1-2402634 |
Discussions on 3-antenna-port codebook-based transmissions |
LG Electronics |
| R1-2402661 |
Discussion on the support of 3-antenna-port CB based transmissions |
Xiaomi |
| R1-2402685 |
Discussion on 3-antenna-port codebook-based transmissions |
Transsion Holdings |
| R1-2402723 |
Discussion on the 3-port codebook-based transmission |
Honor |
| R1-2402768 |
Discussion on 3-antenna-port codebook-based transmissions |
NEC |
| R1-2402793 |
Discussion on uplink enhancement for UE with 3Tx |
Fujitsu |
| R1-2402840 |
On the support for 3-antenna-port codebook-based transmissions |
Nokia |
| R1-2402876 |
Views on R19 3Tx codebook based transmission |
Apple |
| R1-2403099 |
Support for 3 Tx UL transmissions |
Ericsson |
| R1-2403110 |
Support for 3-antenna-port codebook-based transmission |
Sharp |
| R1-2403189 |
3 Tx UL MIMO transmissions |
Qualcomm Incorporated |
| R1-2403239 |
Discussion on support for 3-antenna-port codebook-based transmissions |
NTT DOCOMO, INC. |
| 9.2.4 |
Enhancement for asymmetric DL sTRP/UL mTRP scenarios |
|
| R1-2402020 |
Discussion on power control enhancements for DL sTRP and UL mTRP deployment |
Huawei, HiSilicon |
| R1-2402066 |
Discussion on enhancements for asymmetric DL sTRP/UL mTRP scenarios |
ZTE, China Telecom |
| R1-2402070 |
Enhancement for asymmetric DL sTRP/UL mTRP scenarios |
Ericsson |
| R1-2402082 |
Rel-19 Asymmetric mTRP Operation |
InterDigital, Inc. |
| R1-2402101 |
Enhancements for asymmetric DL sTRP/UL mTRP scenarios |
Spreadtrum Communications |
| R1-2402141 |
Enhancements for asymmetric DL/UL scenarios |
Intel Corporation |
| R1-2402158 |
Enhancement for asymmetric DL sTRP/UL mTRP scenarios |
MediaTek Inc. |
| R1-2402238 |
Discussion on asymmetric DL sTRP/UL mTRP scenarios |
vivo |
| R1-2402288 |
Discussion on asymmetric DL sTRP/UL mTRP scenarios |
TCL |
| R1-2402324 |
Enhancements on asymmetric DL sTRP/UL mTRP scenarios |
OPPO |
| R1-2402379 |
Discussion on asymmetric DL sTRP/UL mTRP scenarios |
CATT |
| R1-2402462 |
Views on Rel-19 asymmetric DL sTRP/UL mTRP scenarios |
Samsung |
| R1-2402499 |
Enhancement for asymmetric DL sTRP/UL mTRP scenarios |
Lenovo |
| R1-2402507 |
Discussion on enhancements for asymmetric DL sTRP/UL mTRP scenarios |
China Telecom, ZTE |
| R1-2402531 |
Discussion on enhancement for asymmetric DL sTRP/UL mTRP scenarios |
Langbo |
| R1-2402561 |
Discussion on enhancement for asymmetric DL sTRP/UL mTRP scenarios |
CMCC |
| R1-2402635 |
Discussions on asymmetric DL sTRP/UL mTRP scenarios |
LG Electronics |
| R1-2402662 |
Discussion on enhancement for asymmetric DL sTRP/UL mTRP scenarios |
Xiaomi |
| R1-2402686 |
Discussion on enhancements for asymmetric DL sTRP/UL mTRP scenarios |
Transsion Holdings |
| R1-2402719 |
Discussion on asymmetric DL sTRP and UL mTRP |
ASUSTeK |
| R1-2402724 |
Discussion on enhancements for asymmetric DL sTRP/UL mTRP scenarios |
Honor |
| R1-2402759 |
Discussion on enhancements for asymmetric DL sTRP and UL mTRP scenarios |
NEC |
| R1-2402794 |
Discussion on UL-only mTRP operation |
Fujitsu |
| R1-2402841 |
Enhancement for asymmetric DL sTRP/UL mTRP scenarios |
Nokia |
| R1-2402877 |
Views on R19 enhancement for asymmetric DL sTRP/UL mTRP |
Apple |
| R1-2402963 |
Considerations on enhancement for asymmetric DL sTRP/UL mTRP scenarios |
Sony |
| R1-2403016 |
Discussion on asymmetric DL_UL mTRP operation |
ETRI |
| R1-2403089 |
Discussion on enhancement for asymmetric DL sTRP and UL mTRP scenarios |
Google |
| R1-2403111 |
Enhancement for asymmetric DL sTRP/UL mTRP scenarios |
Sharp |
| R1-2403132 |
Enhancement for asymmetric DL sTRP/UL mTRP scenarios |
Panasonic |
| R1-2403190 |
Enhancement for asymmetric DL sTRP and UL mTRP deployment scenarios |
Qualcomm Incorporated |
| R1-2403240 |
Discussion on enhancement for asymmetric DL sTRP/UL mTRP scenarios |
NTT DOCOMO, INC. |
| R1-2403414 |
Summary #1 on Rel-19 asymmetric DL sTRP/UL mTRP |
Moderator (OPPO) |
| R1-2403415 |
Summary #2 on Rel-19 asymmetric DL sTRP/UL mTRP |
Moderator (OPPO) |
| R1-2403416 |
Summary #3 on Rel-19 asymmetric DL sTRP/UL mTRP |
Moderator (OPPO) |
| 9.3.1 |
SBFD TX/RX/measurement procedures |
|
| R1-2401980 |
Discussion on SBFD TX/RX/measurement procedures |
TCL |
| R1-2401994 |
On subband full duplex design |
Huawei, HiSilicon |
| R1-2402102 |
Discussion on SBFD TX/RX/measurement procedures |
Spreadtrum Communications |
| R1-2402124 |
On SBFD TX RX and measurement procedures |
InterDigital, Inc. |
| R1-2402165 |
Discussion on transmission, reception and measurement procedures for SBFD operation |
ZTE |
| R1-2402168 |
Discussion for SBFD TX RX measurement procedures |
New H3C Technologies Co., Ltd. |
| R1-2402239 |
Discussion on Rel-19 SBFD operation |
vivo |
| R1-2402325 |
Discussion on SBFD Tx/Rx/measurement procedures |
OPPO |
| R1-2402380 |
Discussion on SBFD TX/RX/measurement procedures |
CATT |
| R1-2402403 |
Discussion for SBFD TX/RX/ measurement procedures |
Tejas Network Limited |
| R1-2402463 |
SBFD operation and procedures |
Samsung |
| R1-2402508 |
Discussion on SBFD TX/RX/measurement procedures |
China Telecom |
| R1-2402532 |
Discussion on SBFD TX/RX/measurement procedures |
Langbo |
| R1-2402562 |
Discussion on SBFD TX/RX/measurement procedures |
CMCC |
| R1-2402595 |
Discussion on SBFD TX/RX/measurement procedures |
MediaTek Inc. |
| R1-2402663 |
Discussion on reception and transmission procedure for SBFD operation |
Xiaomi |
| R1-2402687 |
Discussion on SBFD operation |
Transsion Holdings |
| R1-2402795 |
Discussion on Tx/Rx/measurement procedures for SBFD operation |
Fujitsu |
| R1-2402803 |
SBFD TX/RX/measurement procedures |
Ericsson |
| R1-2402807 |
Discussion on SBFD TX/RX/measurement procedures |
ITRI |
| R1-2402817 |
Tx Rx procedure for SBFD |
ASUSTeK |
| R1-2402824 |
Discussion on subband non-overlapping full duplex Tx-Rx and measurement operations |
NEC |
| R1-2402878 |
Views on SBFD TX/RX/measurement procedures |
Apple |
| R1-2402910 |
Discussion on SBFD TX/RX/measurement procedures |
Panasonic |
| R1-2402925 |
On SBFD TX/RX/measurement procedures |
Nokia, Nokia Shanghai Bell |
| R1-2402964 |
SBFD operations |
Sony |
| R1-2403017 |
Discussion on SBFD TX/RX/measurement procedures |
ETRI |
| R1-2403057 |
Discussion on SBFD TX/RX/ measurement procedures |
CEWiT |
| R1-2403071 |
SBFD procedures in RRC_CONNECTED mode |
Sharp |
| R1-2403095 |
Discussion on SBFD Tx/Rx operation |
Charter Communications, Inc |
| R1-2403162 |
Views on SBFD TX/RX measurement procedures |
Lenovo |
| R1-2403191 |
SBFD Transmission, Reception and Measurement Procedures |
Qualcomm Incorporated |
| R1-2403215 |
Discussion on SBFD TX/RX/measurement procedures |
Google Inc. |
| R1-2403241 |
Discussion on SBFD TX/RX/measurement procedures |
NTT DOCOMO, INC. |
| R1-2403264 |
Discussion on SBFD TX/RX/measurement procedures |
LG Electronics |
| R1-2403307 |
Discussion on SBFD Tx/Rx/measurement procedures |
KT Corp. |
| R1-2403323 |
Discussions on SBFD TX/RX/measurement procedures |
Ruijie Networks Co. Ltd |
| R1-2403369 |
Discussion on SBFD TX/RX/measurement procedures |
WILUS |
| R1-2403377 |
Discussion on SBFD TX/RX operation |
CableLabs |
| R1-2403472 |
Summary #1 of SBFD TX/RX/measurement procedures |
Moderator (CATT) |
| R1-2403473 |
Summary #2 of SBFD TX/RX/measurement procedures |
Moderator (CATT) |
| R1-2403474 |
Summary #3 of SBFD TX/RX/measurement procedures |
Moderator (CATT) |
| 9.3.2 |
SBFD random access operation |
|
| R1-2401981 |
Discussion on SBFD random access operation |
TCL |
| R1-2401995 |
On subband full duplex random access operation |
Huawei, HiSilicon |
| R1-2402103 |
Discussion on SBFD random access operation |
Spreadtrum Communications, BUPT |
| R1-2402125 |
Enhancements on SBFD random access operations |
InterDigital, Inc. |
| R1-2402166 |
Discussion on SBFD random access operation |
ZTE |
| R1-2402169 |
Discussion for SBFD random access operation |
New H3C Technologies Co., Ltd. |
| R1-2402240 |
Discussion on random access for Rel-19 SBFD |
vivo |
| R1-2402326 |
Discussion on SBFD random access operation |
OPPO |
| R1-2402381 |
Discussion on SBFD random access operation |
CATT |
| R1-2402404 |
Discussion on SBFD Random Access Operation |
Tejas Network Limited |
| R1-2402464 |
Random access on SBFD resources |
Samsung |
| R1-2402509 |
Discussion on SBFD random access operation |
China Telecom |
| R1-2402533 |
Discussion on SBFD random access operation |
Langbo |
| R1-2402563 |
Discussion on SBFD random access operation |
CMCC |
| R1-2402596 |
Discussion on SBFD Random Access Operation |
MediaTek Inc. |
| R1-2402664 |
Discussion on SBFD random access operation |
Xiaomi |
| R1-2402688 |
Discussion on SBFD random access operation |
Transsion Holdings |
| R1-2402715 |
Discussion on SBFD random access operation |
Korea Testing Laboratory |
| R1-2402747 |
Discussion on SBFD for random access operation |
SK Telecom |
| R1-2402755 |
Discussion on random access for SBFD |
NEC |
| R1-2402804 |
SBFD Random access operation |
Ericsson |
| R1-2402808 |
Discussion on SBFD random access operation |
ITRI |
| R1-2402818 |
Random access procedure for SBFD |
ASUSTeK |
| R1-2402831 |
Discussion on SBFD random access operation |
Fujitsu |
| R1-2402879 |
Views on SBFD random access operation |
Apple |
| R1-2402911 |
Discussion on SBFD random access operation |
Panasonic |
| R1-2402926 |
SBFD random access operation |
Nokia, Nokia Shanghai Bell |
| R1-2402929 |
SBFD random access operation |
Lenovo |
| R1-2402965 |
SBFD RACH operation |
Sony |
| R1-2403018 |
SBFD random access operation |
ETRI |
| R1-2403072 |
Random access in SBFD symbols |
Sharp |
| R1-2403192 |
SBFD Random Access Operation |
Qualcomm Incorporated |
| R1-2403242 |
Discussion on SBFD random access operation |
NTT DOCOMO, INC. |
| R1-2403265 |
Discussion on SBFD random access operation |
LG Electronics |
| R1-2403332 |
On SBFD random access operation |
Google Inc. |
| R1-2403370 |
Discussion on SBFD random access operation |
WILUS |
| R1-2403437 |
SBFD Random access operation |
Ericsson |
| R1-2403468 |
Summary#1 on SBFD random access operation |
Moderator (CMCC) |
| R1-2403469 |
Summary#2 on SBFD random access operation |
Moderator (CMCC) |
| R1-2403470 |
Summary#3 on SBFD random access operation |
Moderator (CMCC) |
| R1-2403789 |
Final summary on SBFD random access operation |
Moderator (CMCC) |
| 9.3.3 |
CLI handling |
|
| R1-2401996 |
On cross-link interference handling for subband full duplex |
Huawei, HiSilicon |
| R1-2402104 |
Discussion on CLI handling |
Spreadtrum Communications |
| R1-2402126 |
On CLI handling for SBFD operations |
InterDigital, Inc. |
| R1-2402167 |
Discussion on CLI handling for Rel-19 duplex operation |
ZTE |
| R1-2402170 |
Discussion on CLI handling |
New H3C Technologies Co., Ltd. |
| R1-2402241 |
Discussion on CLI handling for Rel-19 NR duplex |
vivo |
| R1-2402327 |
CLI handling in NR duplex operation |
OPPO |
| R1-2402382 |
Discussion on CLI handling for NR duplex evolution |
CATT |
| R1-2402399 |
Discussion on gNB-gNB CLI handling |
Tejas Network Limited |
| R1-2402465 |
Cross-link interference handling for SBFD |
Samsung |
| R1-2402564 |
Discussion on CLI handling |
CMCC |
| R1-2402597 |
Discussion on CLI Handling in SBFD system |
MediaTek Inc. |
| R1-2402665 |
Discussion on CLI handling for SBFD operation |
Xiaomi |
| R1-2402689 |
Discussion on SBFD CLI handling |
Transsion Holdings |
| R1-2402751 |
Discussion on CLI handling |
Panasonic |
| R1-2402805 |
CLI handling |
Ericsson |
| R1-2402825 |
CLI handling for NR duplex operation |
NEC |
| R1-2402880 |
Views on CLI handling |
Apple |
| R1-2402923 |
Cross-link interference management for duplexing evolution |
Lenovo |
| R1-2402927 |
Cross-link interference handling for duplex evolution |
Nokia, Nokia Shanghai Bell |
| R1-2402966 |
CLI handling for SBFD |
Sony |
| R1-2403019 |
Discussion on CLI handling for SBFD operation |
ETRI |
| R1-2403044 |
Discussion on gNB-gNB CLI handling |
Tejas Network Limited |
| R1-2403046 |
Considerations and Recommendations for CLI mitigation for Subband Full Duplex |
Charter Communications, Inc |
| R1-2403058 |
Discussion on CLI handling |
CEWiT |
| R1-2403193 |
Enhancements for CLI handling |
Qualcomm Incorporated |
| R1-2403243 |
Discussion on CLI handling |
NTT DOCOMO, INC. |
| R1-2403266 |
Discussion on CLI handling |
LG Electronics |
| R1-2403330 |
On the gNB-to-gNB CLI and the UE-to-UE CLI handling |
Google Inc. |
| R1-2403371 |
Discussion on CLI handling for evolution of NR duplex operation |
WILUS |
| R1-2403512 |
Summary #1 of CLI handling |
Moderator (Huawei) |
| R1-2403513 |
Summary #2 of CLI handling |
Moderator (Huawei) |
| R1-2403514 |
Summary #3 of CLI handling |
Moderator (Huawei) |
| 9.4 |
Study on solutions for Ambient IoT (Internet of Things) in NR (FS_Ambient_IoT_solutions) |
|
| R1-2403663 |
Session notes for 9.4 (Study on solutions for Ambient IoT in NR) |
Ad-Hoc Chair (Huawei) |
| 9.4.1.1 |
Evaluation assumptions and results |
|
| R1-2401970 |
Evaluation assumptions and results for Ambient IoT |
Ericsson |
| R1-2402011 |
Evaluation methodology and assumptions for Ambient IoT |
Huawei, HiSilicon |
| R1-2402040 |
Discussion on evaluation assumptions and results for Ambient IoT devices |
FUTUREWEI |
| R1-2402072 |
Evaluation assumptions and results for Ambient IoT |
Nokia |
| R1-2402105 |
Discussion on evaluation assumptions and results for Ambient IoT |
Spreadtrum Communications |
| R1-2402137 |
Discussions on deployment scenarios and evaluation assumptions for A-IoT |
Intel Corporation |
| R1-2402184 |
Discussion on Ambient IoT evaluations |
ZTE, Sanechips |
| R1-2402242 |
Evaluation methodologies assumptions and results for Ambient IoT |
vivo |
| R1-2402328 |
Discussion on evaluation assumptions and results for A-IoT |
OPPO |
| R1-2402383 |
The evaluation methodology and preliminary results of Ambient IoT |
CATT |
| R1-2402466 |
Considerations for evaluation assumptions and results |
Samsung |
| R1-2402510 |
Discussion on evaluation assumptions and results for Ambient IoT |
China Telecom |
| R1-2402565 |
Discussion on evaluation methodology and assumptions |
CMCC |
| R1-2402666 |
Evaluation methodology and assumptions for Ambient IoT |
Xiaomi |
| R1-2402826 |
Discussion on ambient IoT evaluation framework |
NEC |
| R1-2402857 |
Evaluation assumptions for Ambient IoT |
InterDigital, Inc. |
| R1-2402881 |
Views on evaluation assumptions and link budget analysis for AIoT |
Apple |
| R1-2402946 |
On evaluation assumptions and results for A-IoT |
MediaTek |
| R1-2402967 |
Evaluation assumptions and results for Ambient IoT |
Sony |
| R1-2403101 |
Discussion on the evaluation assumptions for Ambient IoT devices |
Lenovo |
| R1-2403117 |
Discussion on Ambient IoT evaluation |
LG Electronics |
| R1-2403194 |
Evaluation Assumptions and Results |
Qualcomm Incorporated |
| R1-2403244 |
Study on evaluation assumptions for Ambient IoT |
NTT DOCOMO, INC. |
| R1-2403284 |
Evaluation assumptions for Ambient IoT |
Comba |
| R1-2403397 |
Discussion on Evaluation assumption and preliminary results for AIoT |
IIT Kanpur, Indian Institute of Technology Madras |
| R1-2403515 |
FL summary #1 for Ambient IoT evaluation |
Moderator (CMCC) |
| R1-2403516 |
FL summary #2 for Ambient IoT evaluation |
Moderator (CMCC) |
| R1-2403643 |
FL summary #3 for Ambient IoT evaluation |
Moderator (CMCC) |
| R1-2403768 |
FL summary #4 for Ambient IoT evaluation |
Moderator (CMCC) |
| R1-2403769 |
[draft] LS on Ambient-IoT evaluation scenarios and assumptions |
CMCC |
| R1-2403782 |
LS on Ambient-IoT evaluation scenarios and assumptions |
RAN1, CMCC |
| R1-2403788 |
FL summary (final) for Ambient IoT evaluation |
Moderator (CMCC) |
| R1-2403815 |
Email discussion on Ambient IoT evaluation assumptions |
Moderator (CMCC) |
| 9.4.1.2 |
Ambient IoT device architectures |
|
| R1-2401971 |
Ambient IoT device architectures |
Ericsson |
| R1-2401976 |
Discussion on ambient IoT device architectures |
TCL |
| R1-2402012 |
Ultra low power device architectures for Ambient IoT |
Huawei, HiSilicon |
| R1-2402041 |
Discussion on Ambient IoT device architectures |
FUTUREWEI |
| R1-2402073 |
Ambient IoT device architectures |
Nokia |
| R1-2402106 |
Discussion on Ambient IoT device architectures |
Spreadtrum Communications |
| R1-2402185 |
Discussion on Ambient IoT device architectures |
ZTE, Sanechips |
| R1-2402243 |
Discussion on Ambient IoT Device architectures |
vivo |
| R1-2402329 |
Discussion on device architecture for A-IoT device |
OPPO |
| R1-2402384 |
Study of the Ambient IoT devices architecture |
CATT |
| R1-2402467 |
Considerations for Ambient-IoT device architectures |
Samsung |
| R1-2402511 |
Discussion on Ambient IoT device architectures |
China Telecom |
| R1-2402566 |
Discussion on Ambient IoT device architectures |
CMCC |
| R1-2402667 |
Discussion on ambient IoT device architectures |
Xiaomi |
| R1-2402725 |
Discussion on Ambient IoT device architectures |
Honor |
| R1-2402827 |
Device architecture requirements for ambient IoT |
NEC |
| R1-2402858 |
Device architectures for Ambient IoT |
InterDigital, Inc. |
| R1-2402882 |
Views on device architecture for AIoT |
Apple |
| R1-2402947 |
On Ambient IoT device architectures |
MediaTek |
| R1-2402968 |
Ambient IoT device architectures |
Sony |
| R1-2403059 |
Discussion on Ambient IoT device architectures |
CEWiT |
| R1-2403102 |
Discussion on the Ambient IoT device architectures |
Lenovo |
| R1-2403118 |
Discussion on Ambient IoT device architectures |
LG Electronics |
| R1-2403195 |
Ambient IoT Device Architecture |
Qualcomm Incorporated |
| R1-2403245 |
Study on device architectures for Ambient IoT |
NTT DOCOMO, INC. |
| R1-2403398 |
Views on Architecture of Ambient IoT |
IIT Kanpur, Indian Institute of Tech Madras |
| R1-2403497 |
FL Summary #1 for 9.4.1.2 A-IoT Device Architecture |
Moderator (Qualcomm) |
| R1-2403498 |
FL Summary #2 for 9.4.1.2 A-IoT Device Architecture |
Moderator (Qualcomm) |
| R1-2403499 |
FL Summary #3 for 9.4.1.2 A-IoT Device Architecture |
Moderator (Qualcomm) |
| R1-2403774 |
FL Summary #4 for 9.4.1.2 A-IoT Device Architecture |
Moderator (Qualcomm) |
| 9.4.2.1 |
General aspects of physical layer design |
|
| R1-2401972 |
General aspects of physical layer design for Ambient IoT |
Ericsson |
| R1-2401977 |
Discussion on general aspects of physical layer design for Ambient IoT |
TCL |
| R1-2402013 |
On general aspects of physical layer design for Ambient IoT |
Huawei, HiSilicon |
| R1-2402042 |
Discussion on physical layer design for Ambient IoT devices |
FUTUREWEI |
| R1-2402074 |
General aspects of physical layer design for Ambient IoT |
Nokia |
| R1-2402107 |
Discussion on general aspects of physical layer design for Ambient IoT |
Spreadtrum Communications |
| R1-2402186 |
Discussion on general aspects of physical layer design for Ambient IoT |
ZTE, Sanechips |
| R1-2402244 |
Discussion on General Aspects of Physical Layer Design |
vivo |
| R1-2402330 |
Discussion on general aspects of physical layer design of A-IoT communication |
OPPO |
| R1-2402385 |
Discussion on general aspects of physical layer design |
CATT |
| R1-2402468 |
Considerations on general aspects of Ambient IoT |
Samsung |
| R1-2402487 |
General aspects of physical layer design for Ambient IoT |
Panasonic |
| R1-2402512 |
Discussion on general aspects of physical layer design for Ambient IoT |
China Telecom |
| R1-2402547 |
Discussion on Physical Layer Design for Ambient-IoT |
EURECOM |
| R1-2402567 |
Discussion on general aspects of A-IoT physical layer design |
CMCC |
| R1-2402668 |
Discussion on physical layer design of Ambient IoT |
Xiaomi |
| R1-2402706 |
Considerations on Some Aspects of Physical Layer Design for Ambient IoT |
Continental Automotive |
| R1-2402720 |
Ambient IoT – General aspects of physical layer design, for uplink modulation |
Wiliot Ltd. |
| R1-2402736 |
Discussion on general aspects of physical layer design |
Sharp |
| R1-2402769 |
Discussion on general aspects of ambient IoT physical layer design |
NEC |
| R1-2402859 |
Discussion on general aspects of physical layer design for Ambient IoT |
InterDigital, Inc. |
| R1-2402883 |
Views on general physical layer design aspects for AIoT |
Apple |
| R1-2402948 |
On general aspects of physical layer design for A-IoT |
MediaTek |
| R1-2402969 |
General aspects of physical layer design for Ambient IoT |
Sony |
| R1-2403020 |
Discussion on general aspects of physical layer design |
ETRI |
| R1-2403060 |
Discussion on General aspects of physical layer design |
CEWiT |
| R1-2403069 |
Discussions on general aspects of physical layer design for Ambient IoT |
Ruijie Networks Co. Ltd |
| R1-2403090 |
Discussion on general aspects of physical layer design |
Google |
| R1-2403103 |
Discussion on the physical layer design aspects for Ambient IoT devices |
Lenovo |
| R1-2403119 |
General aspects of Ambient IoT physical layer design |
LG Electronics |
| R1-2403196 |
General aspects of physical layer design |
Qualcomm Incorporated |
| R1-2403246 |
Study on general aspects of physical layer design for Ambient IoT |
NTT DOCOMO, INC. |
| R1-2403281 |
Discussion on general aspects of physical layer design |
Comba |
| R1-2403309 |
General aspects of physical layer design for Ambient IoT |
ITL |
| R1-2403394 |
Discussion on general aspects of physical layer design for AIoT |
IIT Kanpur, Indian Institute of Technology Madras |
| R1-2403445 |
Discussion on general aspects of physical layer design for Ambient IoT |
ZTE, Sanechips |
| R1-2403487 |
Feature Lead Summary#1 for 9.4.2.1: “Ambient IoT – General aspects of physical layer design” |
Moderator (Huawei) |
| R1-2403488 |
Feature Lead Summary#2 for 9.4.2.1: “Ambient IoT – General aspects of physical layer design” |
Moderator (Huawei) |
| R1-2403678 |
Feature Lead Summary#3 for 9.4.2.1: “Ambient IoT – General aspects of physical layer design” |
Moderator (Huawei) |
| R1-2403679 |
Feature Lead Summary#4 for 9.4.2.1: “Ambient IoT – General aspects of physical layer design” |
Moderator (Huawei) |
| 9.4.2.2 |
Frame structure and timing aspects |
|
| R1-2401973 |
Frame structure and timing aspects for Ambient IoT |
Ericsson |
| R1-2402014 |
On frame structure and timing aspects of Ambient IoT |
Huawei, HiSilicon |
| R1-2402043 |
Discussion on Frame Structure and Timing Aspects for Ambient IoT |
FUTUREWEI |
| R1-2402075 |
Frame structure and timing aspects for Ambient IoT |
Nokia |
| R1-2402108 |
Discussion on frame structure and timing aspects for Ambient IoT |
Spreadtrum Communications |
| R1-2402134 |
Discussions on frame structure and timing aspects for A-IoT |
Intel Corporation |
| R1-2402154 |
Discussion on frame structure and timing aspects for Ambient IoT |
BUPT |
| R1-2402187 |
Discussion on frame structure and physical layer procedure for Ambient IoT |
ZTE, Sanechips |
| R1-2402245 |
Discussion on Frame structure, random access, scheduling and timing aspects |
vivo |
| R1-2402331 |
Discussion on frame structure and timing aspects of A-IoT |
OPPO |
| R1-2402386 |
Study of Frame structure and timing aspects for Ambient IoT |
CATT |
| R1-2402469 |
Considerations for frame structure and timing aspects |
Samsung |
| R1-2402513 |
Discussion on frame structure and timing aspects for Ambient IoT |
China Telecom |
| R1-2402568 |
Discussion on frame structure and timing aspects for A-IoT |
CMCC |
| R1-2402585 |
Discussion on physical layer procedures for ambient IoT |
Lenovo |
| R1-2402615 |
Frame structure and timing aspects of Ambient IoT |
InterDigital, Inc. |
| R1-2402669 |
Discussion on frame structure and timing aspects for Ambient IoT |
Xiaomi |
| R1-2402737 |
Discussion on frame structure and timing aspects |
Sharp |
| R1-2402748 |
Discussion on A-IoT Frame Structure and Timing Aspects |
Panasonic |
| R1-2402770 |
Discussion on frame structure and timing for ambient IoT |
NEC |
| R1-2402796 |
Discussion on frame structure and timing aspects |
Fujitsu |
| R1-2402884 |
Frame structure and timing aspects for Ambient IoT |
Apple |
| R1-2402949 |
On frame structure and timing aspects for A-IoT |
MediaTek |
| R1-2402970 |
Frame structure and timing aspects for Ambient IoT |
Sony |
| R1-2403021 |
Discussion on frame structure and timing aspects |
ETRI |
| R1-2403038 |
Discussion on frame structure and timing aspects for AIoT |
TCL |
| R1-2403042 |
Discussion on frame structure and timing aspects for Ambient IoT |
Comba |
| R1-2403061 |
Discussion on Frame structure and timing aspects |
CEWiT |
| R1-2403091 |
Discussion on frame structure and timing aspects |
Google |
| R1-2403120 |
Frame structure and timing aspects for Ambient IoT |
LG Electronics |
| R1-2403197 |
Frame structure and timing aspects |
Qualcomm Incorporated |
| R1-2403247 |
Study on frame structure and timing aspects for Ambient IoT |
NTT DOCOMO, INC. |
| R1-2403373 |
Discussion on Frame structure and timing aspects for A-IoT |
China Unicom |
| R1-2403393 |
Discussion on Frame Structure and Timing Aspects for Ambient IoT |
Indian Institute of Tech (M), IIT Kanpur |
| R1-2403395 |
Discussion on Frame structure and timing aspects for AIoT |
IIT Kanpur, Indian Institute of Technology Madras |
| R1-2403446 |
FL summary #1 on frame structure and timing aspects for Rel-19 Ambient IoT |
Moderator (vivo) |
| R1-2403447 |
FL summary #2 on frame structure and timing aspects for Rel-19 Ambient IoT |
Moderator (vivo) |
| R1-2403448 |
FL summary #3 on frame structure and timing aspects for Rel-19 Ambient IoT |
Moderator (vivo) |
| R1-2403776 |
Final FL summary on frame structure and timing aspects for Rel-19 Ambient IoT |
Moderator (vivo) |
| 9.4.2.3 |
Downlink and uplink channel/signal aspects |
|
| R1-2401974 |
Downlink and uplink channel/signal aspects for Ambient IoT |
Ericsson |
| R1-2401978 |
Discussion on downlink and uplink channel/signal aspects for Ambient IoT |
TCL |
| R1-2402015 |
Physical channels and signals for Ambient IoT |
Huawei, HiSilicon |
| R1-2402044 |
Discussion on D2R and R2D Channel/Signal Aspects for Ambient IoT |
FUTUREWEI |
| R1-2402076 |
R2D and D2R channel/signal aspects for Ambient IoT |
Nokia |
| R1-2402109 |
Discussion on downlink and uplink channel/signal aspects for Ambient IoT |
Spreadtrum Communications |
| R1-2402135 |
Discussions on physical channel and signals for A-IoT |
Intel Corporation |
| R1-2402188 |
Discussion on downlink/uplink channel/signal for Ambient IoT |
ZTE, Sanechips |
| R1-2402246 |
Discussion on Downlink and uplink channel/signal aspects |
vivo |
| R1-2402332 |
Discussion on downlink and uplink channel/signal aspects for A-IoT |
OPPO |
| R1-2402387 |
DL and UL Physical Channels/signals design in support of Ambient IoT devices |
CATT |
| R1-2402470 |
Considerations for downlink and uplink channel/signal aspect |
Samsung |
| R1-2402514 |
Discussion on downlink and uplink channel/signal aspects for Ambient IoT |
China Telecom |
| R1-2402569 |
Discussion on downlink and uplink channel/signal aspects |
CMCC |
| R1-2402586 |
Discussion on channel/signal aspects for ambient IoT |
Lenovo |
| R1-2402616 |
Downlink and uplink channels aspects of Ambient IoT |
InterDigital, Inc. |
| R1-2402670 |
Discussion on downlink and uplink channel_signal aspects for Ambient IoT |
Xiaomi |
| R1-2402705 |
Considerations on downlink and uplink channels/signals for A-IoT |
Continental Automotive |
| R1-2402738 |
Discussion on downlink and uplink channel/signal aspects |
Sharp |
| R1-2402771 |
Discussion on downlink and uplink channel for ambient IoT |
NEC |
| R1-2402797 |
Discussion on downlink and uplink channel/signal aspects |
Fujitsu |
| R1-2402856 |
Discussion on downlink and uplink channels and signals for A-IoT |
Panasonic |
| R1-2402885 |
Views on physical channels/signals and proximity determination for AIoT |
Apple |
| R1-2402950 |
On downlink and uplink channel/signal aspects for A-IoT |
MediaTek |
| R1-2402971 |
Downlink and uplink physical channel for Ambient IoT |
Sony |
| R1-2403022 |
Discussion on downlink and uplink channel/signal aspects for A-IoT |
ETRI |
| R1-2403043 |
Discussion on downlink and uplink channel and signal for Ambient IoT |
Comba |
| R1-2403092 |
Discussion on downlink and uplink transmission aspects |
Google |
| R1-2403121 |
Downlink and uplink channel/signal aspects for Ambient IoT |
LG Electronics |
| R1-2403198 |
Downlink and uplink channel/signal aspects |
Qualcomm Incorporated |
| R1-2403248 |
Study on downlink and uplink channel/signal aspects for Ambient IoT |
NTT DOCOMO, INC. |
| R1-2403374 |
Discussion on downlink and uplink channel aspects for A-IoT |
China Unicom |
| R1-2403396 |
Discussion on Downlink and Uplink channel/signal aspects for AIoT |
IIT Kanpur, Indian Institute of Technology Madras |
| R1-2403558 |
Feature lead summary#1 on downlink and uplink channel/signal aspects |
Moderator (Apple) |
| R1-2403637 |
Feature lead summary#2 on downlink and uplink channel/signal aspects |
Moderator (Apple) |
| R1-2403749 |
Feature lead summary#3 on downlink and uplink channel/signal aspects |
Moderator (Apple) |
| R1-2403786 |
Final FL summary on downlink and uplink channel/signal aspects |
Moderator (Apple) |
| 9.4.2.4 |
Waveform characteristics of carrier-wave provided externally to the Ambient IoT device |
|
| R1-2401975 |
Waveform characteristics of carrier wave provided externally to the Ambient IoT device |
Ericsson |
| R1-2401979 |
Discussion on waveform characteristics of external carrier-wave for Ambient IoT |
TCL |
| R1-2402016 |
On external carrier wave for backscattering based Ambient IoT device |
Huawei, HiSilicon |
| R1-2402045 |
Discussion on External Carrier Waveform Characteristics for Ambient IoT |
FUTUREWEI |
| R1-2402077 |
Waveform characteristics of carrier-wave provided externally to the Ambient IoT device |
Nokia |
| R1-2402110 |
Discussion on waveform characteristics of external carrier-wave for Ambient IoT |
Spreadtrum Communications |
| R1-2402136 |
Discussions on waveform characteristics of carrier-wave for A-IoT |
Intel Corporation |
| R1-2402189 |
Discussion on carrier wave for Ambient IoT |
ZTE, Sanechips |
| R1-2402247 |
Discussion on CW waveform and interference handling at AIoT UL receiver |
vivo |
| R1-2402333 |
Discussion on Waveform characteristics of carrier-wave provided externally to the A-IoT device |
OPPO |
| R1-2402388 |
Discussion on the waveform characteristics of carrier-wave for the Ambient IoT device |
CATT |
| R1-2402471 |
Considerations for waveform characteristics of carrier-wave |
Samsung |
| R1-2402515 |
Discussion on waveform characteristics of carrier-wave provided externally to the Ambient IoT device |
China Telecom |
| R1-2402570 |
Discussion on waveform characteristics of carrier-wave provided externally to the Ambient IoT device |
CMCC |
| R1-2402587 |
Discussion on external carrier wave for ambient IoT |
Lenovo |
| R1-2402671 |
Discussion on waveform characteristics of carrier-wave |
Xiaomi |
| R1-2402739 |
Discussion on waveform characteristics of externally provided carrier-wave |
Sharp |
| R1-2402860 |
Discussion on carrier-wave for Ambient IoT |
InterDigital, Inc. |
| R1-2402886 |
Views on carrier waveform and interference handling for AIoT |
Apple |
| R1-2402951 |
On carrier-wave waveform characteristics for A-IoT |
MediaTek |
| R1-2402972 |
External carrier wave for Ambient IoT |
Sony |
| R1-2403002 |
Discussion on waveform characteristics of carrier-wave for Ambient IoT device |
Panasonic |
| R1-2403023 |
Discussion on waveform characteristics of carrier-wave provided externally to the A-IoT device |
ETRI |
| R1-2403062 |
Discussion on Waveform characteristics of carrier-wave provided externally to the Ambient IoT device |
CEWiT |
| R1-2403093 |
Discussion on waveform characteristics of carrier-wave provided externally to the Ambient IoT device |
Google |
| R1-2403094 |
Considerations for waveform characteristics of carrier-wave |
Semtech Neuchatel SA |
| R1-2403122 |
Considerations on carrier-wave transmission for Ambient IoT |
LG Electronics |
| R1-2403199 |
Waveform characteristics of carrier-wave provided externally to the Ambient IoT device |
Qualcomm Incorporated |
| R1-2403249 |
Study on waveform characteristics of carrier-wave for Ambient IoT |
NTT DOCOMO, INC. |
| R1-2403399 |
Discussion on Carrier wave related aspects for AIoT |
IIT Kanpur, Indian Institute of Technology Madras |
| R1-2403480 |
FL summary#1 on CW waveform characteristics for A-IoT |
Moderator (Spreadtrum Communications) |
| R1-2403559 |
FL summary#2 on CW waveform characteristics for A-IoT |
Moderator (Spreadtrum Communications) |
| R1-2403639 |
FL summary#3 on CW waveform characteristics for A-IoT |
Moderator (Spreadtrum Communications) |
| R1-2403766 |
FL summary#4 on CW waveform characteristics for A-IoT |
Moderator (Spreadtrum Communications) |
| R1-2403767 |
Final FL summary on CW waveform characteristics for A-IoT |
Moderator (Spreadtrum Communications) |
| 9.5 |
Enhancements of network energy savings for NR (Netw_Energy_NR_enh) |
|
| R1-2403272 |
Updated workplan for Rel-19 network energy savings WI |
Rapporteurs (Ericsson, Apple) |
| 9.5.1 |
On-demand SSB SCell operation |
|
| R1-2401985 |
On-demand SSB SCell Operation |
Nokia, Nokia Shanghai Bell |
| R1-2402029 |
Discussion on on-demand SSB SCell operation for NES |
Huawei, HiSilicon |
| R1-2402048 |
Discussion of on-demand SSB Scell operation |
FUTUREWEI |
| R1-2402111 |
Discussion on on-demand SSB SCell operation |
Spreadtrum Communications |
| R1-2402149 |
Design of on-demand SSB SCell operation |
Intel Corporation |
| R1-2402190 |
Discussion on on-demand SSB for NES |
ZTE, Sanechips |
| R1-2402248 |
Discussions on on-demand SSB Scell operation |
vivo |
| R1-2402283 |
On-demand SSB SCell Operation |
Google |
| R1-2402334 |
Discussion on the enhancement to support on demand SSB SCell operation |
OPPO |
| R1-2402389 |
Discussion on on-demand SSB SCell operation |
CATT |
| R1-2402472 |
On-demand SSB SCell operation |
Samsung |
| R1-2402516 |
Discussion on on-demand SSB operation for SCell |
China Telecom |
| R1-2402536 |
Discussion on On-demand SSB SCell operation |
Mavenir |
| R1-2402541 |
Discussion on on-demand SSB SCell operation |
Panasonic |
| R1-2402571 |
Discussion on on-demand SSB SCell operation |
CMCC |
| R1-2402637 |
Discussion on on-demand SSB SCell operation |
InterDigital, Inc. |
| R1-2402672 |
Discussion on on-demand SSB SCell operation |
Xiaomi |
| R1-2402690 |
Discussion on On-Demand SSB SCell operation |
Transsion Holdings |
| R1-2402726 |
Discussion on on-demand SSB SCell operation |
Honor |
| R1-2402809 |
Discussion on On-demand SSB SCell operation |
ITRI |
| R1-2402819 |
On-demand SSB for SCell |
ASUSTeK |
| R1-2402828 |
Discussion on on-demand SSB for SCell operation |
NEC |
| R1-2402832 |
Discussion on on-demand SSB SCell operation |
Fujitsu |
| R1-2402887 |
On-demand SSB SCell Operation |
Apple |
| R1-2402930 |
On-demand SSB SCell operation |
Lenovo |
| R1-2402942 |
On-demand SSB SCell operation |
MediaTek |
| R1-2402973 |
On-demand SSB SCell operation |
Sony |
| R1-2403024 |
Discussion on On-demand SSB SCell operation |
ETRI |
| R1-2403063 |
Discussion on on-demand SSB Scell operation |
CEWiT |
| R1-2403123 |
On-demand SSB SCell operation |
LG Electronics |
| R1-2403134 |
On demand SSB Scell operation for NES |
KDDI Corporation |
| R1-2403200 |
On-demand SSB operation for Scell |
Qualcomm Incorporated |
| R1-2403250 |
Discussion on on-demand SSB SCell operation |
NTT DOCOMO, INC. |
| R1-2403273 |
On-demand SSB SCell operation |
Ericsson |
| R1-2403301 |
Discussion on on-demand SSB SCell operation |
Sharp |
| R1-2403304 |
On-demand SSB SCell operation for NES |
Fraunhofer IIS, Fraunhofer HHI |
| R1-2403308 |
Discussion of on-demand SSB SCell operation |
CAICT |
| R1-2403506 |
Summary #1 of on-demand SSB for NES |
Moderator (LG Electronics) |
| R1-2403507 |
Summary #2 of on-demand SSB for NES |
Moderator (LG Electronics) |
| R1-2403508 |
Summary #3 of on-demand SSB for NES |
Moderator (LG Electronics) |
| R1-2403509 |
Summary #4 of on-demand SSB for NES |
Moderator (LG Electronics) |
| R1-2403765 |
Summary #5 of on-demand SSB for NES |
Moderator (LG Electronics) |
| 9.5.2 |
On-demand SIB1 for idle/inactive mode UEs |
|
| R1-2401986 |
On-demand SIB1 for Idle/Inactive mode UEs |
Nokia, Nokia Shanghai Bell |
| R1-2402030 |
Discussion on on-demand SIB1 for NES |
Huawei, HiSilicon |
| R1-2402049 |
Discussion of on-demand SIB1 for idle/inactive mode UEs |
FUTUREWEI |
| R1-2402112 |
Discussion on on-demand SIB1 for idle/inactive mode UEs |
Spreadtrum Communications |
| R1-2402150 |
Study of on-demand SIB1 for idle/inactive mode UEs |
Intel Corporation |
| R1-2402191 |
Discussion on on-demand SIB1 for UEs in idle or inactive mode |
ZTE, Sanechips |
| R1-2402249 |
Discussions on on-demand SIB1 for idle/inactive mode UEs |
vivo |
| R1-2402284 |
On-demand SIB1 for Idle/Inactive Mode UE |
Google |
| R1-2402335 |
Discussion on the enhancement to support on demand SIB1 for idle/inactive mode UE |
OPPO |
| R1-2402390 |
Discussion on on-demand SIB1 |
CATT |
| R1-2402473 |
On-demand SIB1 for idle/inactive mode UEs |
Samsung |
| R1-2402517 |
Discussion on on-demand SIB1 for idle/inactive mode UEs |
China Telecom |
| R1-2402542 |
Discussion on on-demand SIB1 for idle/inactive mode UEs |
Panasonic |
| R1-2402572 |
Discussion on-demand SIB1 for UEs in idle/inactive mode |
CMCC |
| R1-2402673 |
Discussion on on-demand SIB1 for idle/inactive mode UEs |
Xiaomi |
| R1-2402683 |
Discussion on on-demand SIB1 for idle/inactive mode UEs |
InterDigital, Inc. |
| R1-2402691 |
Discussion on on-demand SIB1 transmission for idle/inactive mode UEs |
Transsion Holdings |
| R1-2402820 |
Triggering of on-demand SIB1 |
ASUSTeK |
| R1-2402823 |
On-demand SIB1 for Idle/Inactive mode UEs |
III |
| R1-2402829 |
Discussion on on-demand SIB1 for UEs in idle/inactive mode |
NEC |
| R1-2402833 |
Discussion on on-demand SIB1 transmission for network energy savings |
Fujitsu |
| R1-2402888 |
On on-demand SIB1 for IDLE/INACTIVE mode UE |
Apple |
| R1-2402931 |
On-demand SIB1 for idle/inactive mode UEs |
Lenovo |
| R1-2402943 |
On-demand SIB1 for idle or inactive mode UEs |
MediaTek |
| R1-2402974 |
Considerations on on-demand SIB1 for idle/inactive mode UEs |
Sony |
| R1-2403003 |
Views on On-demand SIB1 operation for idle/inactive UEs |
Vodafone |
| R1-2403025 |
On-demand SIB1 for idle/inactive mode UEs for NES |
ETRI |
| R1-2403064 |
Discussion on on-demand SIB1 |
CEWiT |
| R1-2403124 |
On-demand SIB1 for idle/inactive mode UEs |
LG Electronics |
| R1-2403201 |
On-demand SIB1 procedure |
Qualcomm Incorporated |
| R1-2403251 |
Discussion on on-demand SIB1 for idle/inactive mode UEs |
NTT DOCOMO, INC. |
| R1-2403274 |
Study of on-demand SIB1 for UEs in idle/inactive mode for NES |
Ericsson |
| R1-2403302 |
Discussion on on-demand SIB1 transmission for idle UEs |
Sharp |
| R1-2403305 |
On-demand SIB1 for NES |
Fraunhofer IIS, Fraunhofer HHI |
| R1-2403390 |
Discussion on On-demand SIB1 for idle/inactive mode UEs |
DENSO CORPORATION |
| R1-2403527 |
FL summary 1 for on-demand SIB1 in idle/inactive mode |
Moderator (MediaTek) |
| R1-2403528 |
FL summary 2 for on-demand SIB1 in idle/inactive mode |
Moderator (MediaTek) |
| R1-2403529 |
FL summary 3 for on-demand SIB1 in idle/inactive mode |
Moderator (MediaTek) |
| R1-2403530 |
FL summary 4 for on-demand SIB1 in idle/inactive mode |
Moderator (MediaTek) |
| R1-2403729 |
FL summary 5 for on-demand SIB1 in idle/inactive mode |
Moderator (MediaTek) |
| R1-2403778 |
Draft LS on the conditions for triggering UL WUS transmission to request on-demand SIB1 |
MediaTek Inc. |
| R1-2403779 |
LS on the conditions for triggering UL WUS transmission to request on-demand SIB1 |
RAN1, MediaTek Inc. |
| 9.5.3 |
Adaptation of common signal/channel transmissions |
|
| R1-2401987 |
Adaptation of common signal/channel transmissions |
Nokia, Nokia Shanghai Bell |
| R1-2402031 |
Adaptation of common signal/channel transmissions |
Huawei, HiSilicon |
| R1-2402050 |
Discussion of the adaptation of common signal/channel transmissions |
FUTUREWEI |
| R1-2402113 |
Discussion on adaptation of common signal/channel transmissions |
Spreadtrum Communications |
| R1-2402151 |
Adaptation of common signal/channel transmissions for Network Energy Saving |
Intel Corporation |
| R1-2402192 |
Discussion on common signal_channel for NES |
ZTE, Sanechips |
| R1-2402250 |
Discussions on adaptation of common signal/channel transmissions |
vivo |
| R1-2402285 |
Adaptation of Common Signals |
Google |
| R1-2402336 |
Discussion on adaptation of common signal/channel transmission |
OPPO |
| R1-2402391 |
Discussion on adaptation of common signal/channel transmissions |
CATT |
| R1-2402405 |
Adaptation of common signal/channel transmissions for network energy saving |
Tejas Network Limited |
| R1-2402474 |
Adaptation of common signal/channel transmissions |
Samsung |
| R1-2402518 |
Discussion on common signal/channel adaptation |
China Telecom |
| R1-2402537 |
SSB beam-specific additional PRACH resource configuration and activation/deactivation |
Mavenir |
| R1-2402543 |
Discussion on adaptation of common signal/channel transmission |
Panasonic |
| R1-2402573 |
Discussion on adaptation of common signal/channel transmissions |
CMCC |
| R1-2402674 |
Discussion on adaptation of common signal and channel transmissions |
Xiaomi |
| R1-2402692 |
Discussion on adaptive transmission of common signal or common channel |
Transsion Holdings |
| R1-2402693 |
Discussion on adaptation of common signal/channel transmissions |
InterDigital, Inc. |
| R1-2402727 |
Discussion on adaptation of common signal channel transmissions |
Honor |
| R1-2402798 |
Discussion on adaptation of common signal/channel transmissions |
Fujitsu |
| R1-2402830 |
Discussion on adaptation of common signal/channel transmissions for Cell DTX/DRX |
NEC |
| R1-2402889 |
On adaptation of common signal/channel for NES enhancements |
Apple |
| R1-2402944 |
Adaptation of common signal/channel transmissions |
MediaTek |
| R1-2402975 |
Considerations on adaptation of common signal/channel transmissions |
Sony |
| R1-2403026 |
Adaptation of common signal/channel transmissions for NES |
ETRI |
| R1-2403047 |
Adaptation of common signals and channels |
Lenovo |
| R1-2403065 |
Discussion on adaptation of common signal and channel transmissions |
CEWiT |
| R1-2403125 |
Adaptation of common signal/channel transmissions |
LG Electronics |
| R1-2403136 |
Adaptation of common signal/channel transmissions |
KDDI Corporation |
| R1-2403137 |
Views on adaptation of common signal/channel transmissions |
KT Corp. |
| R1-2403202 |
Adaptation of common channel transmissions |
Qualcomm Incorporated |
| R1-2403252 |
Discussion on adaptation of common signal/channel transmissions |
NTT DOCOMO, INC. |
| R1-2403275 |
Adaptation of common signal/channel transmissions for NES |
Ericsson |
| R1-2403303 |
Discussion on adaptation of common signal/channel transmissions |
Sharp |
| R1-2403306 |
Adaptation of Common Signals and Channels for NES |
Fraunhofer IIS, Fraunhofer HHI |
| R1-2403391 |
Discussion on Adaptation of common signal/channel transmissions |
DENSO CORPORATION |
| R1-2403531 |
Summary#1 of AI 9.5.3 for R19 NES |
Moderator (Ericsson) |
| R1-2403532 |
Summary#2 of AI 9.5.3 for R19 NES |
Moderator (Ericsson) |
| R1-2403691 |
Summary#3 of AI 9.5.3 for R19 NES |
Moderator (Ericsson) |
| R1-2403692 |
Summary#4 of AI 9.5.3 for R19 NES |
Moderator (Ericsson) |
| R1-2403777 |
Final summary of AI 9.5.3 for R19 NES |
Moderator (Ericsson) |
| 9.6 |
Low-power wake-up signal and receiver for NR (NR_LPWUS) |
|
| R1-2403775 |
Summary of RAN1 agreements on LP-WUS/WUR for NR |
Rapporteur (vivo) |
| 9.6.1 |
LP-WUS and LP-SS design |
|
| R1-2401982 |
Discussion on LP-WUS and LP-SS Design |
TCL |
| R1-2401999 |
Signal Design of LP-WUS and LP-SS |
Huawei, HiSilicon |
| R1-2402046 |
Discussion on LP-WUS and LP-SS Design |
FUTUREWEI |
| R1-2402114 |
Discussion on LP-WUS and LP-SS design |
Spreadtrum Communications |
| R1-2402193 |
Discussion on LP-WUS design |
ZTE, Sanechips |
| R1-2402251 |
Discussion on LP-WUS and LP-SS design |
vivo |
| R1-2402337 |
Signal design for LP-WUS and LP-SS |
OPPO |
| R1-2402392 |
Design of LP-WUS and LP-SS |
CATT |
| R1-2402475 |
Discussion on LP-WUS and LP-SS design |
Samsung |
| R1-2402519 |
Discussion on LP-WUS/LPSS design |
China Telecom |
| R1-2402539 |
Discussion on LP-WUS and LP-SS Design |
EURECOM |
| R1-2402544 |
Discussion on the LP-WUS and LP-SS design |
Panasonic |
| R1-2402574 |
Discussion on LP-WUS and LP-SS design |
CMCC |
| R1-2402610 |
Discussion on LP-WUS and LP-SS design framework for Low power WUS |
InterDigital, Inc. |
| R1-2402617 |
Discussion on LP-WUS and LP-SS design |
Everactive |
| R1-2402675 |
Discussion on LP-WUS and LP-SS design |
Xiaomi |
| R1-2402728 |
Discussion on LP-WUS and LP-SS design |
Honor |
| R1-2402740 |
Discussion on LP-WUS and LP-SS design |
Sharp |
| R1-2402760 |
Discussion on LP-WUS and LP-SS design |
NEC |
| R1-2402834 |
Discussion on LP-WUS and LP-SS design |
Fujitsu |
| R1-2402890 |
LP-WUS and LP-SS design |
Apple |
| R1-2402906 |
LP-WUS and LP-SS design |
Nokia |
| R1-2402952 |
On LP-WUS and LP-SS designs |
MediaTek |
| R1-2402976 |
LP-WUS and LP-SS design |
Sony |
| R1-2403105 |
Discussion on LP-WUS and LP-SS design |
Lenovo |
| R1-2403126 |
Discussion on LP-WUS and LP-SS design |
LG Electronics |
| R1-2403203 |
LP-WUS and LP-SS design |
Qualcomm Incorporated |
| R1-2403253 |
Discussion on LP-WUS and LP-SS design |
NTT DOCOMO, INC. |
| R1-2403276 |
LP-WUS and LP-SS design |
Ericsson |
| R1-2403376 |
On LP-WUS and LP-SS design |
Nordic Semiconductor ASA |
| R1-2403418 |
Discussion on LP-WUS and LP-SS design |
Lenovo |
| R1-2403453 |
LP-WUS and LP-SS design |
Nokia |
| R1-2403554 |
Summary #1 of discussions on LP-WUS and LP-SS design |
Moderator (vivo) |
| R1-2403616 |
Summary #2 of discussions on LP-WUS and LP-SS design |
Moderator (vivo) |
| R1-2403751 |
Summary #3 of discussions on LP-WUS and LP-SS design |
Moderator (vivo) |
| R1-2403770 |
Final summary of discussions on LP-WUS and LP-SS design |
Moderator (vivo) |
| 9.6.2 |
LP-WUS operation in IDLE/INACTIVE modes |
|
| R1-2401983 |
Discussion on LP-WUS Operation in IDLE/INACTIVE modes |
TCL |
| R1-2402000 |
Procedures and functionalities of LP-WUS in IDLE/INACTIVE mode |
Huawei, HiSilicon |
| R1-2402047 |
Discussion on LP-WUS Operation in IDLE/INACTIVE Modes |
FUTUREWEI |
| R1-2402115 |
Discussion on LP-WUS operation in IDLE/INACTIVE modes |
Spreadtrum Communications |
| R1-2402194 |
Discussion on LP-WUS operation in IDLE/INACTIVE mode |
ZTE, Sanechips |
| R1-2402252 |
Discussion on LP-WUS operation in IDLE/INACTIVE modes |
vivo |
| R1-2402338 |
Discussion on LP-WUS operation in RRC_IDLE/INACTIVE modes |
OPPO |
| R1-2402393 |
System design and procedure of LP-WUS operation for UE in IDLE/Inactive Modes |
CATT |
| R1-2402476 |
Discussion on LP-WUS operation in IDLE/INACTIVE modes |
Samsung |
| R1-2402520 |
Discussion on LP-WUS operation in IDLE/INACTIVE modes |
China Telecom |
| R1-2402545 |
Discussion on LP-WUS operation in IDLE/INACTIVE modes |
Panasonic |
| R1-2402575 |
Discussion on LP-WUS operation in IDLE/INACTIVE modes |
CMCC |
| R1-2402611 |
Discussion on LP-WUS operation in IDLE/INACTIVE modes |
InterDigital, Inc. |
| R1-2402676 |
Discussion on LP-WUS operation in Idle/Inactive modes |
Xiaomi |
| R1-2402741 |
Discussion on LP-WUS operation in IDLE/INACTIVE modes |
Sharp |
| R1-2402761 |
Discussion on LP-WUS operation in RRC IDLE/INACTIVE mode |
NEC |
| R1-2402835 |
Discussion on LP-WUS operation in IDLE/INACTIVE mode |
Fujitsu |
| R1-2402891 |
LP-WUS operation in IDLE/INACTIVE modes |
Apple |
| R1-2402893 |
Summary #1 on LP-WUS operation in IDLE/INACTIVE mode |
Moderator (Apple) |
| R1-2402894 |
Summary #2 on LP-WUS operation in IDLE/INACTIVE mode |
Moderator (Apple) |
| R1-2402895 |
Summary #3 on LP-WUS operation in IDLE/INACTIVE mode |
Moderator (Apple) |
| R1-2402907 |
LP-WUS operation in ILDE/Inactive mode |
Nokia |
| R1-2402953 |
On LP-WUS operation in IDLE/INACTIVE modes |
MediaTek |
| R1-2402977 |
LP-WUS operation in IDLE / INACTIVE mode |
Sony |
| R1-2403027 |
Discussion on LP-WUS operation in IDLE/INACTIVE modes |
ETRI |
| R1-2403106 |
Discussion on LP-WUS operation in Idle/Inactive modes |
Lenovo |
| R1-2403127 |
Discussion on LP-WUS operation in IDLE/INACTIVE modes |
LG Electronics |
| R1-2403138 |
Views on LP-WUS operation in IDLE/INACTIVE modes |
KT Corp. |
| R1-2403204 |
LP-WUR operation in idle and inactive modes |
Qualcomm Incorporated |
| R1-2403254 |
Discussion on LP-WUS operation in IDLE/INACTIVE modes |
NTT DOCOMO, INC. |
| R1-2403277 |
LP-WUS operation in IDLE and INACTIVE modes |
Ericsson |
| R1-2403375 |
On LP-WUS operation in IDLE/Inactive |
Nordic Semiconductor ASA |
| 9.6.3 |
LP-WUS operation in CONNECTED modes |
|
| R1-2402001 |
Procedures and functionalities of LP-WUS in CONNECTED mode |
Huawei, HiSilicon |
| R1-2402116 |
Discussion on LP-WUS operation in CONNECTED modes |
Spreadtrum Communications |
| R1-2402195 |
Discussion on LP-WUS operation in CONNECTED mode |
ZTE, Sanechips |
| R1-2402253 |
Discussion on LP-WUS operation in CONNECTED modes |
vivo |
| R1-2402339 |
Consideration on wake-up procedure in connected mode |
OPPO |
| R1-2402394 |
System design and procedure of LP-WUS operation for UE in CONNECTED Modes |
CATT |
| R1-2402477 |
Discussion on LP-WUS operation in CONNECTED modes |
Samsung |
| R1-2402521 |
Discussion on LP-WUS operation in CONNECTED modes |
China Telecom |
| R1-2402546 |
Discussion on LP-WUS operation in CONNECTED mode |
Panasonic |
| R1-2402576 |
Discussion on LP-WUS operation in CONNECTED mode |
CMCC |
| R1-2402588 |
Discussion on LP-WUS operation in CONNECTED modes |
Lenovo |
| R1-2402612 |
Discussion on RRC CONNECTED mode LP-WUS monitoring |
InterDigital, Inc. |
| R1-2402677 |
Discussion on LP-WUS operation in Connected mode |
Xiaomi |
| R1-2402742 |
Discussion on LP-WUS operation in CONNECTED modes |
Sharp |
| R1-2402762 |
Discussion on LP-WUS operation in RRC CONNECTED mode |
NEC |
| R1-2402892 |
LP-WUS operation in CONNECTED modes |
Apple |
| R1-2402898 |
LP-WUS operation in CONNECTED modes |
Apple |
| R1-2402908 |
LP-WUS operation in CONNECTED mode |
Nokia |
| R1-2402954 |
On LP-WUS operation in CONNECTED modes |
MediaTek |
| R1-2402978 |
LP-WUS operation in CONNECTED mode |
Sony |
| R1-2403028 |
Discussion on LP-WUS operation in CONNECTED modes |
ETRI |
| R1-2403037 |
Discussion on LP-WUS procedures in Connected mode |
TCL |
| R1-2403128 |
Discussion on LP-WUS operation in CONNECTED modes |
LG Electronics |
| R1-2403205 |
LP-WUR operation in connected mode |
Qualcomm Incorporated |
| R1-2403255 |
Discussion on LP-WUS operation in CONNECTED mode |
NTT DOCOMO, INC. |
| R1-2403278 |
LP-WUS operation in CONNECTED mode |
Ericsson |
| R1-2403517 |
FL summary #1 on LP-WUS operation in CONNECTED mode |
Moderator (NTT DOCOMO) |
| R1-2403713 |
FL summary #2 on LP-WUS operation in CONNECTED mode |
Moderator (NTT DOCOMO) |
| R1-2403714 |
FL summary #3 on LP-WUS operation in CONNECTED mode |
Moderator (NTT DOCOMO) |
| 9.7 |
Study on channel modelling for Integrated Sensing And Communication (ISAC) for NR (FS_Sensing_NR) |
|
| R1-2403664 |
Session notes for 9.7 (Study on channel modelling for Integrated Sensing And Communication for NR) |
Ad-Hoc Chair (Huawei) |
| 9.7.1 |
ISAC deployment scenarios |
|
| R1-2401997 |
Deployment scenarios for ISAC channel model |
Huawei, HiSilicon |
| R1-2402117 |
Discussion on ISAC deployment scenarios |
Spreadtrum Communications |
| R1-2402131 |
Deployment scenarios for ISAC channel modeling |
Intel Corporation |
| R1-2402177 |
Discussion on ISAC deployment scenarios and requirements |
EURECOM |
| R1-2402254 |
Views on Rel-19 ISAC deployment scenarios |
vivo |
| R1-2402289 |
Discussion on ISAC Deployment Scenarios |
Nanjing Ericsson Panda Com Ltd |
| R1-2402340 |
Discussion on ISAC deployment scenarios |
OPPO |
| R1-2402395 |
Discussion on ISAC deployment scenarios |
CATT, CICTCI |
| R1-2402478 |
Discussion on ISAC deployment scenarios |
Samsung |
| R1-2402522 |
Discussion on ISAC deployment scenarios |
China Telecom |
| R1-2402577 |
Discussion on ISAC deployment scenarios |
CMCC, China Southern Power Grid |
| R1-2402599 |
Discussion on ISAC deployment scenarios |
Nokia, Nokia Shanghai Bell |
| R1-2402607 |
Overview of ISAC Deployment scenarios |
Tiami Networks |
| R1-2402678 |
Deployment scenarios and evaluation assumptions for ISAC channel |
Xiaomi |
| R1-2402703 |
Discussion on ISAC deployment scenarios |
ZTE Corporation |
| R1-2402815 |
Discussion on ISAC deployment scenarios |
LG Electronics |
| R1-2402851 |
Deployment scenarios for integrated sensing and communication with NR |
NVIDIA |
| R1-2402896 |
Discussion on ISAC deployment scenarios |
Apple |
| R1-2402914 |
Discussion on ISAC deployment scenarios |
InterDigital, Inc. |
| R1-2402940 |
Discussion on ISAC deployment scenario |
MediaTek |
| R1-2402979 |
Discussion on ISAC Deployment Scenarios |
Sony |
| R1-2403048 |
FL Summary #1 on ISAC Deployment Scenarios |
Moderator (AT&T) |
| R1-2403049 |
FL Summary #2 on ISAC Deployment Scenarios |
Moderator (AT&T) |
| R1-2403050 |
FL Summary #3 on ISAC Deployment Scenarios |
Moderator (AT&T) |
| R1-2403070 |
Discussions on ISAC deployment scenarios |
Ruijie Networks Co. Ltd |
| R1-2403087 |
Discussion on ISAC deployment scenarios |
Lenovo |
| R1-2403133 |
Discussion on ISAC Deployment Scenarios |
Panasonic |
| R1-2403142 |
Deployment Scenarios for ISAC Channel Modeling |
AT&T, FirstNet |
| R1-2403159 |
Considerations on ISCA deployment scenarios |
CAICT |
| R1-2403206 |
Discussion on ISAC deployment scenarios |
Qualcomm Incorporated |
| R1-2403256 |
Study on deployment scenarios for ISAC channel modelling |
NTT DOCOMO, INC. |
| R1-2403386 |
Discussion on ISAC Deployment Scenarios |
IIT Kanpur, Indian Institute of Technology Madras |
| 9.7.2 |
ISAC channel modelling |
|
| R1-2401998 |
Channel modeling methodology for ISAC |
Huawei, HiSilicon |
| R1-2402118 |
Discussion on ISAC channel modeling |
Spreadtrum Communications |
| R1-2402132 |
Discussion on ISAC channel modeling |
Intel Corporation |
| R1-2402178 |
Discussion on ISAC channel modeling |
EURECOM |
| R1-2402255 |
Views on Rel-19 ISAC channel modelling |
vivo |
| R1-2402290 |
Discussion on ISAC Channel Modelling |
Nanjing Ericsson Panda Com Ltd |
| R1-2402341 |
Study on ISAC channel modelling |
OPPO |
| R1-2402396 |
Discussion on ISAC channel modelling |
CATT, CICTCI |
| R1-2402408 |
Discussion on ISAC channel modelling |
SHARP |
| R1-2402479 |
Discussion on ISAC channel modelling |
Samsung |
| R1-2402523 |
Discussion on ISAC channel modelling |
China Telecom |
| R1-2402578 |
Discussion on channel modeling methodology for ISAC |
CMCC, BUPT, SEU, PML |
| R1-2402600 |
Discussion on ISAC channel modelling |
Nokia, Nokia Shanghai Bell |
| R1-2402608 |
ISAC Channel Modeling Considerations |
Tiami Networks |
| R1-2402679 |
Discussion on ISAC channel model |
Xiaomi, BUPT |
| R1-2402680 |
Summary #1 on ISAC channel modelling |
Moderator (Xiaomi) |
| R1-2402681 |
Summary #2 on ISAC channel modelling |
Moderator (Xiaomi) |
| R1-2402682 |
Summary #3 on ISAC channel modelling |
Moderator (Xiaomi) |
| R1-2402704 |
Discussion on channel modelling for ISAC |
ZTE Corporation, BJTU |
| R1-2402708 |
Discussion on ISAC channel modeling |
BUPT, CMCC |
| R1-2402816 |
Discussion on ISAC channel modelling |
LG Electronics |
| R1-2402852 |
Channel modeling for integrated sensing and communication with NR |
NVIDIA |
| R1-2402897 |
Discussion on ISAC channel modelling |
Apple |
| R1-2402915 |
Discussion on ISAC channel modeling |
InterDigital, Inc. |
| R1-2402941 |
Discussion on ISAC channel modelling |
MediaTek |
| R1-2402980 |
Discussion on ISAC Channel Model |
Sony |
| R1-2403078 |
Discussion on Channel Modelling for ISAC |
Lenovo |
| R1-2403107 |
Information on ISAC channel modeling |
Nokia, NIST, Anritsu, Keysight, AT&T, Ericsson, Sharp, NYU Wireless, Motorola Mobility, Futurewei |
| R1-2403135 |
Discussion ISAC channel modelling |
Panasonic |
| R1-2403143 |
Discussions on ISAC Channel Modeling |
AT&T |
| R1-2403160 |
Considerations on ISAC channel modelling |
CAICT |
| R1-2403207 |
Discussion on ISAC channel modelling |
Qualcomm Incorporated |
| R1-2403262 |
Discussion on channel modeling for Integrated Sensing and Communication (ISAC) |
Southeast University |
| R1-2403372 |
Discussions on ISAC Channel Modelling |
ITL |
| R1-2403382 |
Discussion on ISAC channel modeling in automotive |
DENSO CORPORATION |
| R1-2403715 |
Summary #4 on ISAC channel modelling |
Moderator (Xiaomi) |
| R1-2403716 |
Summary #5 on ISAC channel modelling |
Moderator (Xiaomi) |
| 9.8 |
Study on channel modelling enhancements for 7-24GHz for NR (FS_NR_7_24GHz_CHmod) |
|
| R1-2402128 |
Work Plan for Study on 7-24 GHz Channel Modeling Enhancements |
Intel Corporation, ZTE |
| R1-2402619 |
Skeleton of the CR for TR 38.901 |
ZTE,Intel Corporation |
| R1-2403665 |
Session notes for 9.8 (Study on channel modelling enhancements for 7-24GHz for NR) |
Ad-Hoc Chair (CMCC) |
| 9.8.1 |
Channel model validation of TR38.901 for 7-24GHz |
|
| R1-2402009 |
Considerations on the 7-24 GHz channel model validation |
Huawei, HiSilicon, Tongji University |
| R1-2402090 |
On Channel Model Validation of TR38.901 for 7-24GHz |
InterDigital, Inc. |
| R1-2402129 |
Discussion on channel modeling verification for 7-24 GHz |
Intel Corporation |
| R1-2402256 |
Views on channel model validation of TR38.901 for 7-24GHz |
vivo |
| R1-2402397 |
Discussion on channel model validation of TR38.901 for 7-24GHz |
CATT |
| R1-2402407 |
Channel Model Validation of TR 38.901 for 7-24 GHz |
SHARP, NYU WIRLESS |
| R1-2402480 |
Discussion on channel model validation of TR38.901 for 7-24GHz |
Samsung |
| R1-2402601 |
Discussion on Channel model validation of TR38.901 for 7-24GHz |
Nokia |
| R1-2402613 |
Discussion on validation of channel model |
Ericsson |
| R1-2402620 |
Discussion on the channel model validation |
ZTE |
| R1-2402853 |
Channel model validation of TR 38901 for 7-24 GHz |
NVIDIA |
| R1-2402899 |
On Channel Model Validation of TR 38.901 for 7-24 GHz |
Apple |
| R1-2403144 |
Discussion on Validation of the Channel Model in 38901 |
AT&T |
| R1-2403208 |
Channel Model Validation of TR38.901 for 7-24 GHz |
Qualcomm Incorporated |
| R1-2403261 |
Changes to TR 38 901 |
Spark NZ Ltd |
| R1-2403267 |
Discussion on channel model validation of TR38.901 for 7-24GHz |
LG Electronics |
| R1-2403280 |
Discussion on channel model validation of TR38.901 for 7-24GHz |
BUPT, Spark NZ Ltd |
| R1-2403441 |
Summary of issues for Rel-19 7-24 GHz Channel Modeling Validation |
Moderator (Intel Corporation) |
| R1-2403442 |
Summary #1 of discussions for Rel-19 7-24 GHz Channel Modeling Validation |
Moderator (Intel Corporation) |
| R1-2403443 |
Summary #2 of discussions for Rel-19 7-24 GHz Channel Modeling Validation |
Moderator (Intel Corporation) |
| R1-2403630 |
Summary #3 of discussions for Rel-19 7-24 GHz Channel Modeling Validation |
Moderator (Intel Corporation) |
| R1-2403631 |
Summary #4 of discussions for Rel-19 7-24 GHz Channel Modeling Validation |
Moderator (Intel Corporation) |
| 9.8.2 |
Channel model adaptation/extension of TR38.901 for 7-24GHz |
|
| R1-2402010 |
Considerations on the 7-24 GHz channel model extension |
Huawei, HiSilicon, Tongji University |
| R1-2402091 |
On Channel Model Extension of TR38.901 for 7-24GHz |
InterDigital, Inc. |
| R1-2402130 |
Discussion on channel model adaptation/extension |
Intel Corporation |
| R1-2402257 |
Views on channel model adaptation/extension of TR38.901 for 7-24GHz |
vivo |
| R1-2402398 |
Discussion on channel model adaptation/extension of TR38.901 for 7-24GHz |
CATT |
| R1-2402481 |
Discussion on channel model adaptation/extension of TR38.901 for 7-24GHz |
Samsung |
| R1-2402500 |
Discussion of FR3 channel model |
Lenovo |
| R1-2402602 |
Discussion on Channel model adaptation/extension of TR38.901 for 7-24GHz |
Nokia |
| R1-2402614 |
Discussion on adaptation and extension of channel model |
Ericsson |
| R1-2402621 |
Discussion on the channel model adaptation and extension |
ZTE |
| R1-2402854 |
Channel model adaptation of TR 38901 for 7-24 GHz |
NVIDIA |
| R1-2402900 |
On Channel Model Adaptation/Extension of TR 38.901 for 7-24 GHz |
Apple |
| R1-2402938 |
Discussion on channel modelling enhancements for 7-24GHz for NR |
MediaTek |
| R1-2403066 |
Channel model adaptation/extension of TR38.901 for 7-24 GHz |
CEWiT |
| R1-2403086 |
Views on Channel Model Adaption/Extension of TR 38.901 for 7-24 GHz |
SHARP |
| R1-2403209 |
Channel Model Adaptation/Extension of TR38.901 for 7-24GHz |
Qualcomm Incorporated |
| R1-2403268 |
Discussion on channel modelling adaptation/extension for 7-24GHz |
LG Electronics |
| R1-2403285 |
Discussion on modeling near-field propagation and spatial non-stationarity in TR38.901 for 7-24GHz |
BUPT, CMCC |
| R1-2403366 |
Channel model adaptation/extension of TR38.901 for 7-24 GHz |
Keysight Technologies UK Ltd |
| R1-2403541 |
Summary#1 of channel model adaptation and extension |
Moderator (ZTE) |
| R1-2403608 |
Summary#2 of channel model adaptation and extension |
Moderator (ZTE) |
| R1-2403609 |
Summary#3 of channel model adaptation and extension |
Moderator (ZTE) |
| R1-2403718 |
Summary#4 of channel model adaptation and extension |
Moderator (ZTE) |
| 9.10 |
XR (eXtended Reality) for NR Phase 3 (NR_XR_Ph3) |
|
| R1-2403287 |
Work Plan for Rel-19 on XR Enhancements for NR |
Nokia, Qualcomm (Rapporteurs) |
| 9.10.1 |
Enabling TX/RX for XR during RRM measurements |
|
| R1-2402028 |
Discussions on scheduling enhancements considering RRM measurements for XR |
Huawei, HiSilicon |
| R1-2402119 |
Discussion on enabling TX/RX for XR during RRM measurements |
Spreadtrum Communications |
| R1-2402196 |
Discussion on measurement gap for XR |
ZTE, Sanechips |
| R1-2402258 |
Enabling TX/RX for XR during RRM measurements |
vivo |
| R1-2402268 |
Enabling TX/RX for XR during RRM measurements |
TCL |
| R1-2402342 |
Enhancements to enable TX/RX for XR during RRM measurements |
OPPO |
| R1-2402371 |
Signaling control of scheduling restriction during measurement gap in support of XR services |
CATT |
| R1-2402482 |
Discussion on enabling TX/RX for XR during RRM measurements |
Samsung |
| R1-2402579 |
Discussion on enabling TX/RX for XR during RRM measurements |
CMCC |
| R1-2402593 |
RRM measurement gap and scheduling restriction enhancements to TX/RX XR traffic |
Ericsson |
| R1-2402654 |
Discussion on enabling TX/RX for XR during RRM measurements |
Xiaomi |
| R1-2402694 |
Discussion on enabling TX/RX for XR during RRM measurements |
InterDigital, Inc. |
| R1-2402763 |
Discussion on enabling TX/RX for XR during RRM measurements |
NEC |
| R1-2402836 |
Enhancements to enable TX/RX for XR during RRM measurements |
Fraunhofer IIS, Fraunhofer HHI |
| R1-2402855 |
Discussion on enabling TX/RX for XR during RRM measurements |
Panasonic |
| R1-2402901 |
Views on enabling TX/RX for XR during RRM measurements |
Apple |
| R1-2402924 |
Enabling TX/RX for XR during RRM measurements |
Lenovo |
| R1-2402956 |
Enabling TX RX for XR during RRM measurements |
MediaTek |
| R1-2402981 |
On Enabling Tx/Rx for XR during RRM measurements |
Sony |
| R1-2402992 |
Discussion on Enabling TX/RX for XR During RRM Measurements |
Meta |
| R1-2403129 |
Discussion on XR during RRM measurements |
LG Electronics |
| R1-2403149 |
Discussion for enabling TX/RX for XR during RRM measurements |
III |
| R1-2403210 |
Enabling Tx/Rx for XR during RRM measurements |
Qualcomm Incorporated |
| R1-2403257 |
Discussion on enabling TX/RX for XR during RRM |
NTT DOCOMO, INC. |
| R1-2403286 |
Enabling TX/RX for XR during RRM measurements |
Nokia |
| R1-2403329 |
On enabling Tx Rx for XR during RRM measurements |
Google Inc. |
| R1-2403510 |
Moderator summary #1 - Enabling TX/RX for XR during RRM measurements |
Moderator (Nokia) |
| R1-2403511 |
Moderator summary #2 - Enabling TX/RX for XR during RRM measurements |
Moderator (Nokia) |
| R1-2403675 |
Moderator summary #3 - Enabling TX/RX for XR during RRM measurements |
Moderator (Nokia) |
| R1-2403676 |
Moderator summary #4 - Enabling TX/RX for XR during RRM measurements |
Moderator (Nokia) |
| 9.11 |
Non-Terrestrial Networks (NTN) for NR Phase 3 and Internet of Things (IoT) Phase 3 (NR_NTN_Ph3/IoT_NTN_Ph3) |
|
| R1-2401990 |
Work plan for Rel-19 NR_NTN_Ph3 |
THALES |
| R1-2403666 |
Session notes for 9.11 (Non-Terrestrial Networks for NR Phase 3 and Internet of Things Phase 3) |
Ad-Hoc Chair (Huawei) |
| 9.11.1 |
NR-NTN downlink coverage enhancement |
|
| R1-2401988 |
Discussion on NR NTN Downlink coverage enhancements |
THALES |
| R1-2401991 |
FL Summary #1: NR-NTN downlink coverage enhancements |
THALES |
| R1-2401992 |
FL Summary #2: NR-NTN downlink coverage enhancements |
THALES |
| R1-2401993 |
FL Summary #3: NR-NTN downlink coverage enhancements |
THALES |
| R1-2402003 |
Discussion on downlink coverage enhancements for NR NTN |
Huawei, HiSilicon |
| R1-2402078 |
On NR-NTN downlink coverage enhancement |
Ericsson |
| R1-2402120 |
Discussion on NR-NTN downlink coverage enhancement |
Spreadtrum Communications |
| R1-2402173 |
NR-NTN downlink coverage enhancement |
InterDigital, Inc. |
| R1-2402259 |
Discussion on NR-NTN downlink coverage enhancement |
vivo |
| R1-2402286 |
Downlink Coverage Enhancement for NR NTN |
Google |
| R1-2402343 |
Discussion on NR-NTN downlink coverage enhancement |
OPPO |
| R1-2402372 |
Performance evaluation of downlink coverage enhancement for NR NTN |
CATT |
| R1-2402483 |
Discussion on downlink coverage enhancement for NR-NTN |
Samsung |
| R1-2402580 |
Discussion on NR-NTN DL coverage enhancement |
CMCC |
| R1-2402589 |
Discussion on downlink coverage enhancement for NR NTN |
Lenovo |
| R1-2402622 |
Discussion on DL coverage enhancement for NR NTN |
ZTE |
| R1-2402655 |
Discussion on NR-NTN downlink coverage enhancement |
Xiaomi |
| R1-2402752 |
Discussion on downlink coverage enhancement for NR NTN |
Baicells |
| R1-2402772 |
NR-NTN downlink coverage enhancement |
NEC |
| R1-2402811 |
Discussion on NR-NTN downlink coverage enhancement |
LG Electronics |
| R1-2402845 |
Discussion on downlink coverage enhancement for NR-NTN |
CSCN |
| R1-2402902 |
On NR-NTN Downlink Coverage Enhancement |
Apple |
| R1-2402916 |
NR-NTN downlink coverage enhancement with beam groups |
Sharp |
| R1-2402934 |
Discussion on NR-NTN downlink coverage enhancement |
MediaTek |
| R1-2403029 |
Discussion on NR-NTN downlink coverage enhancement |
ETRI |
| R1-2403067 |
Downlink Coverage Enhancements for NR NTN |
CEWiT |
| R1-2403080 |
Downlink coverage enhancements for NR over NTN |
Nokia, Nokia Shanghai Bell |
| R1-2403139 |
Discussion on DL coverage enhancements for NR-NTN |
NICT |
| R1-2403211 |
Downlink coverage enhancement for NR NTN |
Qualcomm Incorporated |
| R1-2403258 |
Discussion on DL coverage enhancement for NR-NTN |
NTT DOCOMO, INC. |
| R1-2403283 |
NR-NTN Downlink Coverage Enhancement |
Panasonic |
| R1-2403387 |
Discussion on NR-NTN DL coverage enhancement |
Inmarsat, Viasat |
| R1-2403403 |
On the SAN phased-array antenna characteristics |
ESA |
| R1-2403412 |
Downlink Coverage Enhancements for NR NTN |
CEWiT |
| 9.11.2 |
Support of RedCap and eRedCap UEs with NR NTN operating in FR1-NTN bands |
|
| R1-2402004 |
Discussion on HD-FDD RedCap UEs and eRedCap UEs for FR1-NTN |
Huawei, HiSilicon |
| R1-2402121 |
Discussion on support of RedCap and eRedCap UEs with NR NTN operating in FR1-NTN bands |
Spreadtrum Communications |
| R1-2402174 |
Discussion on half-duplex RedCap issues for NTN FR1 operation |
InterDigital, Inc. |
| R1-2402260 |
Discussion on support of RedCap and eRedCap UEs with NR-NTN |
vivo |
| R1-2402344 |
Discussion on supporting of RedCap and eRedCap UEs with NR NTN operating in FR1-NTN bands |
OPPO |
| R1-2402373 |
Discussion on the operation of RedCap and eRedCap UEs In NTN |
CATT |
| R1-2402484 |
Discussion on support of RedCap and eRedCap UEs with NR NTN operating in FR1-NTN bands |
Samsung |
| R1-2402524 |
Discussion on Support of RedCap and eRedCap UEs with NR NTN operating in FR1-NTN bands |
China Telecom |
| R1-2402581 |
Discussion on the collision issues of HD-FDD Redcap UE in FR1-NTN |
CMCC |
| R1-2402623 |
Discussion on support of RedCap/eRedCap UEs for NR NTN |
ZTE |
| R1-2402656 |
Discussion on the support of Redcap UE for NTN operating on FR1 bands |
Xiaomi |
| R1-2402729 |
Discussion on support of RedCap/eRedCap UEs in NR NTN |
Honor |
| R1-2402812 |
Discussion on support of (e)RedCap UEs with NR-NTN operating in FR1-NTN bands |
LG Electronics |
| R1-2402903 |
On support of RedCap UEs with NR NTN operation |
Apple |
| R1-2402935 |
Discussion on support of RedCap and eRedCap UEs with NR NTN operating in FR1-NTN bands |
MediaTek |
| R1-2403004 |
On HD-FDD Redcap UEs for NTN |
Ericsson |
| R1-2403030 |
Discussion on HD UEs with NR NTN |
ETRI |
| R1-2403039 |
Discussion on HD-FDD RedCap UEs and eRedCap UEs for FR1-NTN |
TCL |
| R1-2403081 |
Considerations for RedCap HD-FDD operation for NR over NTN |
Nokia, Nokia Shanghai Bell |
| R1-2403161 |
Discussion on support of RedCap/eRedCap UEs in NTN |
CAICT |
| R1-2403212 |
Support of Redcap and eRedcap UEs in NR NTN |
Qualcomm Incorporated |
| R1-2403259 |
Discussion on support of RedCap and eRedCap UEs in FR1-NTN |
NTT DOCOMO, INC. |
| R1-2403633 |
Summary #1 for Support of RedCap and eRedCap UEs with NR NTN operating in FR1-NTN bands |
Moderator (CATT) |
| R1-2403743 |
Summary #2 for Support of RedCap and eRedCap UEs with NR NTN operating in FR1-NTN bands |
Moderator (CATT) |
| R1-2403787 |
Summary #3 for Support of RedCap and eRedCap UEs with NR NTN operating in FR1-NTN bands |
Moderator (CATT) |
| 9.11.3 |
NR-NTN uplink capacity/throughput enhancement |
|
| R1-2402005 |
Discussion on uplink capacity/throughput enhancement for FR1-NTN |
Huawei, HiSilicon |
| R1-2402122 |
Discussion on NR-NTN uplink capacity/throughput enhancement |
Spreadtrum Communications |
| R1-2402175 |
NR-NTN uplink capacity/throughput enhancement |
InterDigital, Inc. |
| R1-2402261 |
Discussion on NR-NTN uplink capacity enhancement |
vivo |
| R1-2402287 |
Uplink Capacity Enhancement for NR NTN |
Google |
| R1-2402345 |
Discussion on NR-NTN uplink capacity/throughput enhancement |
OPPO |
| R1-2402374 |
Discussion on UL capacity enhancement for NR NTN |
CATT |
| R1-2402485 |
Discussion on uplink capacity/throughput enhancement for NR-NTN |
Samsung |
| R1-2402525 |
Discussion on NR-NTN uplink enhancement |
China Telecom |
| R1-2402534 |
Discussion on Uplink Capacity/Throughput Enhancement for NR-NTN |
Langbo |
| R1-2402582 |
Discussion on the NR-NTN uplink capacity/throughput enhancements |
CMCC |
| R1-2402594 |
On uplink capacity/throughput enhancement for NR NTN |
Ericsson |
| R1-2402624 |
Discussion on UL capacity enhancement for NR NTN |
ZTE |
| R1-2402657 |
Discussion on NR-NTN PUSCH capacity enhancement |
Xiaomi |
| R1-2402773 |
NR-NTN uplink capacity/throughput enhancement |
NEC |
| R1-2402813 |
Discussion on NR-NTN uplink capacity/throughput enhancement |
LG Electronics |
| R1-2402904 |
On NR-NTN Uplink Capacity Enhancement |
Apple |
| R1-2402936 |
Discussion on NR-NTN uplink capacity and throughput |
MediaTek |
| R1-2402995 |
Uplink capacity/throughput enhancement for NR-NTN |
Panasonic |
| R1-2403031 |
Discussion on NR-NTN uplink capacity/throughput enhancement |
ETRI |
| R1-2403040 |
Discussion on NR-NTN uplink capacity/throughput enhancement |
TCL |
| R1-2403077 |
Discussion on uplink capacity/throughput enhancement for NR-NTN |
Lenovo |
| R1-2403082 |
Uplink capacity enhancement considerations for NR over NTN |
Nokia, Nokia Shanghai Bell |
| R1-2403140 |
Discussion on NR-NTN uplink capacity/throughput enhancement |
NICT |
| R1-2403213 |
NR-NTN uplink capacity - throughput enhancement |
Qualcomm Incorporated |
| R1-2403260 |
Discussion on NR-NTN uplink capacity/throughput enhancement |
NTT DOCOMO, INC. |
| R1-2403388 |
Discussion on NR-NTN UL capacity-throughput enhancements |
Inmarsat, Viasat |
| R1-2403402 |
Views on NR-NTN PUSCH capacity enhancement |
Mitsubishi Electric RCE |
| R1-2403422 |
Feature lead summary #1 of AI 9.11.3 on NR-NTN uplink capacity and throughput |
Moderator (MediaTek) |
| R1-2403423 |
Feature lead summary #2 of AI 9.11.3 on NR-NTN uplink capacity and throughput |
Moderator (MediaTek) |
| R1-2403721 |
Feature lead summary #3 of AI 9.11.3 on NR-NTN uplink capacity and throughput |
Moderator (MediaTek) |
| 9.11.4 |
IoT-NTN uplink capacity/throughput enhancement |
|
| R1-2402006 |
Discussion on UL capacity enhancements for IoT NTN |
Huawei, HiSilicon |
| R1-2402123 |
Discussion on IoT-NTN uplink capacity/throughput enhancement |
Spreadtrum Communications |
| R1-2402176 |
IoT-NTN uplink capacity/throughput enhancement |
InterDigital, Inc. |
| R1-2402262 |
Discussion on IoT-NTN uplink capacity enhancement |
vivo |
| R1-2402346 |
Discussion on IoT-NTN uplink capacity/throughput enhancement |
OPPO |
| R1-2402375 |
Discussion on UL capacity enhancement for IoT NTN |
CATT |
| R1-2402486 |
Discussion on uplink capacity/throughput enhancement for IoT-NTN |
Samsung |
| R1-2402583 |
Discussion on the IoT -NTN uplink capacity/throughput enhancements |
CMCC |
| R1-2402590 |
Discussion on uplink capacity enhancement for IoT NTN |
Lenovo |
| R1-2402625 |
Discussion on UL capacity enhancement for IoT NTN |
ZTE |
| R1-2402658 |
Discussion on IoT-NTN uplink capacity enhancement |
Xiaomi |
| R1-2402774 |
IoT-NTN uplink capacity/throughput enhancement |
NEC |
| R1-2402814 |
Discussion on IoT-NTN uplink capacity/throughput enhancement |
LG Electronics |
| R1-2402905 |
On IoT-NTN Uplink Capacity Enhancement |
Apple |
| R1-2402917 |
IoT NTN OCC methods for NPUSCH and NPRACH |
Sharp |
| R1-2402937 |
Discussion on IoT-NTN uplink capacity and throughput |
MediaTek |
| R1-2402994 |
IoT-NTN uplink capacity enhancement |
Nokia, Nokia Shanghai Bell |
| R1-2403005 |
On uplink capacity enhancements for IoT-NTN |
Ericsson |
| R1-2403032 |
Discussion on IoT-NTN uplink capacity/throughput enhancement |
ETRI |
| R1-2403214 |
IOT-NTN uplink capacity - throughput enhancement |
Qualcomm Incorporated |
| R1-2403389 |
Discussion on IoT-NTN UL capacity enhancements |
Inmarsat, Viasat |
| R1-2403444 |
IOT-NTN uplink capacity - throughput enhancement |
Qualcomm Incorporated |
| R1-2403560 |
FL Summary #1 for IoT-NTN |
Moderator (Sony) |
| R1-2403719 |
FL Summary #2 for IoT-NTN |
Moderator (Sony) |